Browse documentation

Troubleshooting

A workflow is not running

Check Active status, saved validation, trigger matching, selected number, schedule timezone, and webhook input.

Automation buildersBeginnerAvailable

What this guide covers

  • No execution usually points to status or trigger matching rather than a later node.
  • Prerequisites: Workflow name/ID, event time, number, and trigger type.
  • Result: A controlled matching event produces a new execution.
  • Limit: Pausing prevents new starts but does not retroactively remove evidence from older executions.

What this is and when to use it

No execution usually points to status or trigger matching rather than a later node.

When to use A workflow is not running
Use it whenExpected outcome
A matching business event appears not to start the workflow.A controlled matching event produces a new execution.

Before you begin

  1. Workflow name/ID, event time, number, and trigger type.

Complete the task

  1. Confirm status is Active and the canvas shows Saved.
  2. Open Workflow Trigger and compare every event filter.
  3. For messages, verify the connected number and message/keyword match.
  4. For schedules, verify recurrence, timezone, and future occurrence.
  5. For webhooks, confirm the exact generated URL and request arrival.
  6. Reproduce in Test.

Confirm it worked

  1. A controlled matching event produces a new execution.

Common problems

A workflow is not running troubleshooting
SymptomWhat to check
Workflow is draft or pausedActivate it after validation.
Keyword case or mode does not matchCorrect contains, exact, or starts-with configuration.

Current limitations

Pausing prevents new starts but does not retroactively remove evidence from older executions.

Where to go next