Automations
Run history and debugging
Reading a run log, retries, and why a step did not fire.
Open a run
- Open Automations and select the workflow.
- Open the Runs tab. The newest 25 runs are shown first.
- Select a run to inspect its contact, times, status, step log, and trigger data.
- Check the version number in the Runs list before comparing the log with the current draft.
Read the run status
Pending
The run has been created and is waiting for a worker.
Running
The worker is executing the current step.
Waiting
A wait has a future resume time, or a failed step is in retry backoff.
Completed
All steps finished, or a continue-if condition intentionally stopped the run.
Failed
The same step failed on the third attempt.
Cancelled
The run was cancelled and will not be processed again.
Read the step log
Each attempt records the step number, action type, status, finish time, and either its output, skip reason, or error. A retry creates another log entry at the same step number, which makes repeated failures visible instead of overwriting the first attempt.
Completed
The provider or data operation succeeded. Expand the output when shown.
Skipped
Nothing was sent or changed, usually because required contact data was absent or a condition was false.
Failed
The action returned an error. The run retries or ends depending on its attempt count.
Automatic retries
A failed step is attempted up to three times in total. After the first failure, the run waits about two minutes; after the second, about four minutes. The third failure marks the run Failed. Successful earlier actions are not repeated because the run keeps its cursor on the failed step.
Why a workflow did not fire
- Confirm the workflow is Active, not Draft, Paused, or Archived.
- Confirm the latest edits were published, not only saved.
- Check that the event belongs to the same client workspace.
- Review form, tag, pipeline, and stage filters for an exact match.
- Review every trigger condition; all of them must pass.
- Check Settings: with re-enrolment off, a contact that has any earlier run will not enter again.
- For schedules, confirm the expression is valid UTC cron and the maintenance sweep is operating.
Why a step did not act
- Open the step's skip reason or error instead of relying only on the overall Completed status.
- Confirm the run has a contact and that the contact has the email, phone, or open deal the action needs.
- Check email and SMS consent, provider connections, and the selected workspace member.
- For a webhook, inspect the returned status and body and confirm the URL is public and responds within 15 seconds.
- Compare the run's published version with the draft currently visible in the builder.
Trigger data at the bottom of the run shows the exact event fields available to conditions and templates. Use it to spot a wrong field key or an unexpected source value.