Zap and step run statuses indicate whether your Zap or specific steps ran successfully or not. A Zap run status may differ from the statuses of its individual steps. There are six possible Zap statuses:

• Filtered.
• Held.
• Playing.
• Stopped.
• Success.
• Waiting.

You can view them in your Zap history or in the Zap runs sidebar in the Zap editor. This article explains what each status means.

Note

Human in the Loop actions may have special run statuses.

Filtered

The filtered status indicates that the conditions in a Filter step were not met, so the Zap did not run any subsequent steps. It's identified by the filter icon .

Held

The held status indicates that the run is paused. You can attempt to replay held Zaps or steps. It's identified by the pause icon . Learn why held runs occur and how to troubleshoot them.

Playing

The playing status indicates that the run is in progress. It's identified by the play icon .

Stopped

The stopped status indicates that the run had an issue and could not be completed. It's identified by the hand icon . The stopped status is subdivided into three sub-statuses:

• Errored.
• Halted.
• Handled.

Errored

The errored sub-status indicates that the run encountered an error.

• If a step errors, subsequent Zap steps that depend on fields mapped from this step will also error.
• If a Zap errors repeatedly each time it runs, it will automatically turn off.
  • Learn how to troubleshoot errors in Zaps.

Halted

The halted sub-status indicates that the run stopped on purpose. This usually occurs in search action steps when they find no results.

• If subsequent Zap steps have required fields mapped from this step, they will error.
• Unlike the errored sub-status, a Zap will not automatically turn off if a Zap halts multiple times.

Handled

The handled sub-status indicates that an error handler ran as an alternative workflow, after the Zap or step run encountered an error. Unlike the errored sub-status, a Zap will not turn off automatically if a Zap's error is labeled as "handled" multiple times.

Success

The successful status indicates that the run completed. It's identified by the check mark icon .

Waiting

The waiting status indicates that the Zap is waiting to complete one or more steps. It's identified by the clock icon . The waiting status is subdivided into two sub-statuses:

Delayed

The delayed sub-status indicates that the Zap run has a delay step that is postponing the completion of the Zap run. The Zap will run the step after the delay period.

Scheduled

The scheduled sub-status indicates that the Zap run is scheduled to re-run because it encountered an error, but autoreplay is enabled in your account. When it re-runs:

• If it is successful, the status will change to “Success”.
• If it is unsuccessful, the status will change to “Stopped/Errored”.

Deleting Zap runs

A Zap run's status determines what happens when you delete a Zap run.

If you see a filtered, held, stopped, or success status, the Zap finished running the action. Deleting the Zap run only removes the record of the run. It cannot undo the action.

If you see a playing or waiting status, the Zap has not finished running the action yet. Deleting the Zap run prevents the Zap from finishing the run. It also deletes the record of the run.

Additional Info

• Zap run statuses may be caused by more than one issue.
• You can replay Zap steps or entire runs that failed or were not successful.
• If the Zap polls for new data and does not trigger, this will not appear in Zap history.
• When a Paths step runs, as long as all other steps are successful:
  • If a path’s conditions are met, the path and the Zap will both have Success statuses.
  • If a path’s conditions are not met, the path will have a Filtered status and the Zap will have a Success status.