You can test an automation in two ways. A manual run does the real work. A simulated run only walks through the steps. To start either, you need to be a workspace admin of the workspace the database app is in.
Note:
A manual run has real effects. Records change, comments appear, and emails go out. It also counts toward your usage.
A manual run follows your filters. A manual run passes no field changes, so
Has changedandHas changed todon't match and the record is skipped. To test such a filter, change the field on a test record so a real run starts, or useIswhile you test.A paused automation can still run manually. Pausing doesn't protect against
Manual run.A simulated run still calls other services. Requests from
Send HTTP request,Send API request, and thehttpclient inExecute scriptare sent for real. In a script, checkcurrent_workflow_is_simulationto skip such calls.
Start a manual run
Open the automation in the editor.
Select
Manual run. Hover over it to seeStart a manual run. The shortcut iscmd/ctrl+J. You also findManual runin the•••menu in the header of the editor.Next to
Run on, chooseSelected records,Selected view,Number of records, orAll records. WithSelected records, pick records from the list. Each shows the record name of its database app and the workspace, for exampleExpense in Accounting.Select
Start run. If you have unsaved changes, the button readsSave and start runand saves them first.
You can't start a manual run on a draft record.
For triggers without a record, such as On a scheduled time or interval, the run needs no record. For When a webhook is received, the run uses data from a webhook. Next to Run on, choose Last payload to reuse the last data received, or Custom payload to paste your own.
To run on all records of a database app, read Run an automation on existing records →.
Start a simulated run
Click
•••in the header of the editor.Select
Simulated run. The shortcut iscmd/ctrl+K.Next to
Simulate on, choose the records, the same way as for a manual run.Select
Start simulation.
A simulated run skips the filter and doesn't change data. Use Manual run to test the filter. Actions that would change something, such as updating a record, adding a comment, or creating a record, only pretend to do it. Their steps still show Success, but nothing changes. The trigger and the filter show Skipped. Use it to check the structure of an automation and the values you insert. A simulated run doesn't send emails, but requests to other services go out for real.
Check the result
Click
▷next toManual run. Hover over it to seeView all runs. You can also presscmd/ctrl+1.Find your run. Manual runs are listed as
Manual run onwith a date and time. Runs started by the trigger are listed asRun on. Simulated runs are listed asSimulated run onwith a date and time.Select the run to see each step and its status, such as
SuccessorSkipped.
Learn more in Automation runs →.
Test an automation safely
Use a few records that don't matter.
Start with
Simulated run, then useManual runon one record.Set the automation to
Pausedwhile you test, so real changes don't start it. Learn more in Active, paused, and broken automations →.
Learn more
FAQs
Can I run a paused automation manually?
Can I run a paused automation manually?
Yes, Manual run works while the automation is Paused. Only the trigger is paused.
Can I restart a failed run?
Can I restart a failed run?
No, a failed run can't be restarted from the run itself. Fix the cause, then start a Manual run for the affected records.
Does a simulated run send emails?
Does a simulated run send emails?
No, a simulated run doesn't send emails, and it doesn't change records. Requests to other services, for example with Send HTTP request, are still sent.
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: Run and simulate in the developer docs →
Still have more questions? Find answers and get help from community experts in the Tape community →.
