A run is one execution of an automation. It shows which record started it, which steps ran, and how each step ended. You can use runs for many things, including:
Finding out why a reminder email didn't go out.
Checking that a new automation did what you expected.
Note:
Runs are kept for 30 days. Older runs are deleted.
Filters decide if a run appears. If a record doesn't match the filter, no run appears.
Who can use automation runs?
Automations are available on the Free, Plus, and Premium plans. The number of automation actions per month depends on your plan. See the limits for your plan on our pricing page.
Workspace admins can see the runs of the automations in their workspaces.
The
Runslist in the Automation Center shows runs of the database apps you haveFull accessto.
See the runs of one automation
Open the automation in the Automation editor →.
Click
▷next toManual run. Hover over it to see the tooltipView all runs. The shortcut iscmd/ctrl+1. The runs panel opens on the right.
The panel lists the runs, newest first. Each entry has a date and a status:
Run onand a date and time is a normal run.Manual run onand a date and time is a run you started withManual run.Simulated run onand a date and time is a run fromSimulated run. Learn more in Test automations →.
At the top of the panel, Follow turns on notifications. Hover over it to see Receive notifications for all failed runs.
Read a run
Select a run to open its steps. Each step has a status next to it. The steps follow the automation from top to bottom:
The trigger reads like
When a record is updatedtriggered byRecord IDfollowed by a number. The number is the ID of the record that started the run.The filter step,
And if the following conditions are met, shows whether the record matched.Actions that change a record read like
Add a comment to the current recordperformed onRecord IDand a number. It tells you which record the action worked on, which can be a different record than the one that started the run.
A step has one of these statuses:
Successmeans the step worked.Skippedmeans the step didn't do anything. You see it for the trigger in manual and simulated runs, and for the filter in simulated runs.Failedmeans the step failed.Cancelledmeans the run was stopped before the step finished.In progressmeans the step is still running.
The run shows Failed at the top. To see why, expand the failed step: its log shows the error message in red, starting with Action execution failed with error:.
See the runs of all automations
Open the Automation Center → and select Runs. Simulated runs don't appear here, only in the runs panel of the automation. The list has the columns Run, Date and time, App, Automation, and Status.
Search with
Search runs….Filter by
App,Automation, orStatus.Click
⟳(Refresh) at the top right to reload the list. If you're an organization owner or admin,•••next to it hasWebhook notificationsandExport runs.
Run statuses
Scheduled: The run is waiting to start.Running(shown asIn progressin the run): The run is in progress.Success: The run finished without an error.Throttled: Tape slowed down your organization for a short time because of a lot of activity. The run starts on its own when it lifts. Learn more in Automation limits and throttling →.Failed: A step failed and stopped the run, unlessContinue on erroris on for it. Learn more in Handle errors in automations →.Cancelled: The run was stopped withCancel runsbefore it finished. A run that takes too long fails instead.
Cancel or export runs
In the editor, click ••• at the top right to see Cancel runs and Export runs.
Cancel runsstops all scheduled and running runs of this automation after you confirm.Export runsdownloads a CSV file with the runs of this automation from the last 14 days, one row per step.
Automation run errors
A run fails if it takes longer than three minutes or uses more than 1,000 actions. Learn more in Automation limits and throttling →.
A failed run shows the reason, for example
Workflow timeoutorAction execution failed.For help with messages in a failed step, read Common automation errors →.
Test, pause, edit, or delete an automation
Runs don't change when you edit an automation. To change what future runs do, edit the automation and select Save changes. Each run keeps the version of the automation that ran. When you open an older run, it shows the steps as they were at that time, even if you changed the automation since.
Learn more
FAQs
Why is there no run for my record?
Why is there no run for my record?
If the record didn't match the filter, the automation doesn't create a run. Check the trigger and the filter, then read My automation isn't running →.
What's the difference between Run on and Simulated run on?
What's the difference between Run on and Simulated run on?
Run on is a real run. Simulated run on is a test that didn't change any data.
How do I get notified when a run fails?
How do I get notified when a run fails?
Click ▷ next to Manual run and select Follow at the top of the panel. You get notifications for all failed runs of that automation.
Can I see runs of automations in other apps?
Can I see runs of automations in other apps?
Yes! Open Runs in the Automation Center and use the App filter.
Are you a developer using the Tape API for automations?
Are you a developer using the Tape API for automations?
The automation API has its own documentation for developers. Full reference: Automation run in the developer docs →
Still have questions? Find answers and get help from community experts in the Tape community →
