Why didn't my workflow run, or why is it stuck in Pending?
Open the workflow's History and click Details on the run to see whether it started, which conditions passed and which step failed. Pending means it is queued.
- Verified Nov 22, 2026
- Classic builder
On this page
Open the workflow, click History, set the date to when you expected it to run and click Details on the run: it shows each record, which conditions passed (Rules checked) and which step failed and why. No run at all means the workflow did not start. Pending means the run is queued and waiting to start, which can take a while when many runs are waiting.
No run in History #
| Cause | Fix |
|---|---|
| The workflow is Inactive. | Switch it to Active at the top of the editor and save. |
| The trigger does not match the change, for example Record Created when you edited a record. | Use Record Updated or Record Created or Updated. |
| The change was made by the same workflow, or by a chain of more than five workflows starting each other. | Do the work in the first workflow, or start the other one from a step. |
| Hourly or Every Minute is not in your plan. | Choose Daily or longer, or change plan. |
It ran, but not as expected #
- Condition not met: compare Value found with the rule under Rules checked. A field that was empty when the run started is a common cause.
- Skipped: a scheduled run is skipped when the previous run was still going, and every run is skipped when the workflow has no steps.
- This step failed: the step shows the error, Why and What to do. Fix the cause, then use Rerun to run only the failed records again.
- To watch or cancel runs that are queued or in progress, click Running in the editor.
See Fix a workflow that does not run as expected for the full list.
Was this page helpful?
Something wrong or missing on this page? Tell us.