Help · Automation and workflows
Why my workflow did not run
The handful of reasons an automation stays quiet — inactive, a trigger that never fired, a condition that excluded everything, or an action that failed — and how to tell which.
Updated August 2026
A workflow that does nothing gives you no error message, because from its point of view nothing has gone wrong. Diagnosing it is a matter of working down a short list in order.
Who this is for
Anyone whose automation is not doing what they expected.
Before you start
- The workflow in front of you.
- A specific record you expected it to act on — a concrete case is far easier to debug than a general feeling.
Check active first, every time
The most common cause by a wide margin is that the workflow was never activated. Drafts do not run. This is especially easy to hit with an installed template or a workflow created by an agent, both of which arrive as drafts by design. Check this before investigating anything else.
Work down the list
- Is it active?
Drafts do not run. Templates install as drafts and agent-created workflows are forced to draft, so this catches most cases immediately. - Did the trigger actually fire?
Check whether the event genuinely happened. A trigger on a field that nobody changed will never fire, however correct the rest of the flow is. - Did the condition exclude it?
This is the second most common cause. Run a dry run and look at the count — a condition matching zero records looks identical to a broken workflow. - Read the run history
If the flow ran, the history shows what happened, including an action that failed. A run that appears here did fire, which changes the diagnosis entirely. - Retry a failed run
Where an action failed for a transient reason, retrying is the fix. Where it failed for a real reason, the history tells you which action and why. - Check permissions and prerequisites
An action that needs something absent — a sending mailbox, an integration — cannot complete. The run history usually says so.
What you get
- An ordered diagnosis instead of guessing.
- The distinction between never ran and ran-and-failed.
- A retry path for transient failures.
- Confidence about whether the trigger or the condition is at fault.
Frequently asked questions
What is the single most common cause?
The workflow was never activated. Drafts do not run, and both templates and agent-created workflows arrive as drafts deliberately.
How do I tell whether it ran at all?
Run history. If there is no run, the trigger did not fire or the condition excluded everything. If there is a run, read what it did.
How do I test a condition without waiting for a trigger?
Dry-run it and look at the match count. Zero matches is the answer to most 'it does not run' questions.
An action failed. Can I just retry it?
Yes, and for a transient failure that is the fix. Read why it failed first — a retry does not help if the cause is a missing prerequisite.
Related articles
Dry-run a workflow before turning it on
See what a workflow would do without it doing anything. The dry run is the cheapest way to find out that your condition matches four thousand records instead of four.
Read articleRead run history and retry
Open any run to see a per-node trace, find the step that failed and why, retry from the failed step, and rely on idempotency keys, loop guards, and an on-failure recovery branch.
Read articleTriggers, conditions and branches
How a workflow knows when to run and where to go: the events that trigger it, the AND/OR conditions that filter it, and the branches that route a run down the right path.
Read articleHave an account issue this guide doesn't cover?
Start free today
Ready to give your team a CRM they'll actually use?
Start free. Bring your whole team. Cancel whenever (you won't).