Workflow not triggering
- Confirm the workflow status is Active and the last change was saved with Publish this version now.
- Check the trigger matches the real event. Message Received via Email only fires for senders who are already contacts. Triggered from Broadcast must be attached to the broadcast.
- For store events, verify the event was received (21. External Integrations).
- Open Last 10 executions. A run that ended after a FALSE condition did trigger; the condition just didn’t match.
WhatsApp auto-reply works for some people but not new numbers
- The first step must be Add/Upsert Contact. Without it, steps fail with "…requires a contact context" for numbers that are not contacts yet (11.11).
Auto-reply never matches
- Message Matches with Contains and a long sentence rarely matches what people type. Use short keywords and Equals for commands (11.20).
Customer got two replies
- Two active workflows on the same trigger both run. Combine them with conditions.
- Store events fire their specific trigger and External Integration Event Received (11.8).
Workflow execution failed
- Open Last 10 executions on the Workflow List and read the failed step’s message.
- Match it in Errors While a Workflow Runs. Common causes: no contact (add Add/Upsert Contact), plain-text WhatsApp outside the 24-hour window (use a template), template no longer approved, contact without email, or no mailbox.
- Fix the cause, then Retry failed execution to resume from the failed step.
"N step(s) are not connected to the flow" when saving
- Connect each listed step from Start or an earlier step, or delete it (11.5).
"Check before saving" appears
- The designer spotted a likely mistake, for example a contact step without Add/Upsert Contact before it. Read each point; Save anyway only if it is intended (11.24).
Delay not advancing
- Due runs are processed periodically. Wait a few minutes. If a run is stuck for more than an hour, contact support.
