S-Chain Pipeline Issues - December 10, 2025
Resolved 💬 2 comments Opened Dec 10, 2025 by mark-bfd Closed Dec 10, 2025
S-Chain Daily Update - December 10, 2025
Issues Identified
1. Template Variable Passthrough (${emailTitle})
- Location: WF2S AI4 Enhancement node
- Problem: Marketing emails (e.g., Qualcomm/Marketo) contain template variables like
${emailTitle}in body_text - Impact: AI4 passes these through literally into
pubspoke_content_body_content - Affected Record: Qualcomm (WF2S ID 379, WF3S ID 352)
- Fix Needed: Strip template variables (pattern:
\${[^}]+}) from body_text before AI processing
2. Body Content Truncation
- Location: WF2S AI4 Enhancement output
- Problem: AI output truncates body content significantly
- Example: Qualcomm source 3549 chars → AI output 2033 chars (42% loss)
- Fix Needed: AI4 prompt needs explicit instruction to preserve FULL content
3. Same Title Across All Tabs
- Status: FIXED in WF3S v76
- Fix: page_title now uses original PR headline instead of creative title
- Verified: Qualcomm now shows different titles for article_heading vs page_title
Fixes Applied Today
| Fix | Location | Status |
|-----|----------|--------|
| Contact exclusion (Scott St. John) | WF2S v262 | ✅ Verified working |
| Page description period | WF2S v262 | ✅ Working for new records |
| Page title differentiation | WF3S v76 | ✅ Deployed and verified |
| Period fix for existing WF3S records | SQL manual fix | ✅ Applied to IDs 352, 357 |
| Qualcomm page_title | SQL manual fix | ✅ Fixed |
Outstanding Pipeline Fixes Required
- WF2S v263: Add Code node to strip template variables from body_text before AI4
- WF2S AI4 prompt: Add instruction to preserve complete body content without truncation
Database Records Status
Qualcomm (message_id: 720662265.594493637.1765376295431@abmktmail-batch1k.marketo.org)
- WF2S ID: 379
- WF3S ID: 352
- Issues: ${emailTitle} in body, truncated content
- Article already in Pubspoke - requires manual content fix in Pubspoke UI
🤖 Generated with Claude Code
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗