Zap run details provide information about the Zap, such as the Zap run status and data received and sent by each step. You can review individual Zap runs by selecting them from the Zap runs section in the left sidebar of the Zap editor.
Review a Zap run
Zap runs in the left sidebar
In the left sidebar, click the Zap runs icon to review recent Zap runs. You can select a Zap run card from the list, you will enter the run view. The right sidebar will open and the Zap outline will expand with additional info about the run. Each run will have a Zap run status and each step will have a separate step run status. For example, if the Zap run errors, you may still have individual steps in the Zap run that were successful.
Zap outline in the center
At the top of the Zap outline, there is:
- The Zap run status.
- A link to view the Zap run in the Zap history page.
- A timestamp of the run date.
- The Zap version used for that run.
- The run ID. Each Zap run has a unique ID.
You can find more details for each step in a Zap run. Each step shows:
- The step run status icon.
- The app used in the step.
- The step number and app event used in the step.
- A description of the trigger event or action event that occurred.
- If the Zap run is not successful, you will find additional details why.
Step run details in the right sidebar
When you select a step in the Zap outline, you can review specific information about what occurred in that step. There are four possible tabs to help you review, depending on whether its a trigger or action step and the step run status.
- Data In: the data that was sent to the connected app for the given step.
- Data Out: the data that was received from the connected app for the given step.
- Troubleshoot: an AI-powered troubleshooting guide for errored Zap runs.
- Logs: a detailed HTTP log for the step that can be used for troubleshooting.
- Logs may take up to 3 minutes to load.
- Logs are only available for up to 7 days after a step runs, including replay attempts.

If your Zap errors, reviewing a Zap run can help you pinpoint the problem. Learn how to troubleshoot errors in Zaps.
0 comments
Article is closed for comments.