Journey Not Sending — 360° Check
Systematic troubleshooting path for a Journey Builder audience that entered incorrectly or did not send.
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.
Confirm entry source
Validate the correct DE/API event, entry schedule, re-entry policy and version are active.
Validate source data
Check sendability, SubscriberKey mapping, required email/mobile attributes, nulls and data types.
Check contact/subscriber state
Inspect All Subscribers / channel status, suppression logic, held/bounced/unsubscribed state and BU context.
Check permissions & classification
Validate explicit opt-in model, publication lists, send classification, sender profile and domain configuration.
Inspect Journey execution
Check entry history, decision split logic, waits, goals/exits, contact frequency rules and version status.
Inspect send/tracking
Resolve the email JobID and query _Sent/_Bounce/_Open/_Click as appropriate.
Check operational constraints
Look for throttling, send windows, data refresh timing and upstream automation failures.
Document the root cause
Capture the failing condition and add a regression check to the runbook or automation.