The Journey Is Running. The Triggered Send Is Not.
Contacts enter the Journey, but an email activity appears to stop sending or a queue starts building.
Trust & provenancePRODUCTION
Evidence tierPRODUCTIONOfficial sources2Other sources0Last verifiedNot recorded
Evidence tier describes my hands-on relationship with the content. Official sources describe platform contracts/documentation. Production observations should not automatically be treated as official limits.
Journey status and the underlying triggered-send state are separate operational signals. Salesforce explicitly calls out a Running Journey with a Stopped/Error triggered send as a cause of send failure/backlog.
What to check
- Journey History: did the contact actually reach the activity?
- Email Studio → Interactions → Triggered Sends: is the related send Stopped/Error?
- Inspect queue age/depth and recent content/personalization changes.
Make it cheaper next time
- Add triggered-send health to post-deploy verification.
- When throughput drops, inspect the send layer before rebuilding the Journey.
journey buildertriggered sendqueueemail