Automation Flow Execution Issues

This guide helps you diagnose and fix automation flows that fail to run, stop partway through, or behave differently than you expect.

Flow Does Not Trigger

Issue: Your flow never starts, even when the triggering event happens.

Possible Causes:

1. The flow is disabled or in draft status
2. The trigger conditions do not match the incoming event
3. Another flow or rule handled the event first
4. The channel or integration that should fire the trigger is disconnected

Solutions:

• Confirm the flow is published and set to Active, not Draft or Paused
• Re-check the trigger conditions and compare them against a real example event
• Make sure no higher-priority flow is consuming the same trigger
• Verify the connected channel (for example WhatsApp or Messenger) is online

Flow Stops Midway

Issue: The flow starts but stops before reaching the end.

Possible Causes:

1. A step is waiting on a condition or a customer reply that never arrives
2. A required variable or field is empty at that step
3. An external action (such as a webhook or API call) failed
4. The flow hit a delay or wait step that has not completed yet

Solutions:

• Open the flow run history and find the exact step where it stopped
• Check whether a wait or delay step is still counting down
• Ensure variables used by the step are populated earlier in the flow
• Review logs for any failed external action and retry once the cause is fixed

Wrong Branch or Condition Result

Issue: The flow runs but takes the wrong path through a conditional branch.

Possible Causes:

1. Condition logic compares the wrong field or uses the wrong operator
2. Values are formatted differently than expected (for example text versus number)
3. Multiple conditions overlap and the first match is not the one you intended

Solutions:

• Review each condition and confirm it references the correct variable
• Normalize data formats (trim spaces, match case, convert types) before comparing
• Order conditions from most specific to most general so the right branch matches first

Scheduled or Delayed Messages Arrive Late

Issue: Messages scheduled by the flow are delayed.

> Info: Short delays are normal during high traffic. Persistent delays usually point to a queue backlog or a disconnected channel.

Solutions:

• Confirm the destination channel is connected and within its sending limits
• Check that the scheduled time accounts for the correct time zone
• Review the status page for processing delays

Still Having Issues?

If your flow still misbehaves:

• Use the flow run history to capture the exact step and error
• Note the trigger event and the data that started the run
• Contact our support team with the flow name, the run timestamp, and a description of the expected versus actual behavior