RUNBOOK // sfmcPRODUCTION

Journey Not Sending — 360° Check

Systematic troubleshooting path for a Journey Builder audience that entered incorrectly or did not send.

Context Pack →Open Workspace →
Trust & provenancePRODUCTION
Evidence tierPRODUCTIONOfficial sources0Other 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.

01

Confirm entry source

Validate the correct DE/API event, entry schedule, re-entry policy and version are active.

02

Validate source data

Check sendability, SubscriberKey mapping, required email/mobile attributes, nulls and data types.

03

Check contact/subscriber state

Inspect All Subscribers / channel status, suppression logic, held/bounced/unsubscribed state and BU context.

04

Check permissions & classification

Validate explicit opt-in model, publication lists, send classification, sender profile and domain configuration.

05

Inspect Journey execution

Check entry history, decision split logic, waits, goals/exits, contact frequency rules and version status.

06

Inspect send/tracking

Resolve the email JobID and query _Sent/_Bounce/_Open/_Click as appropriate.

07

Check operational constraints

Look for throttling, send windows, data refresh timing and upstream automation failures.

08

Document the root cause

Capture the failing condition and add a regression check to the runbook or automation.