Say you build an automation that fills a new field when a task is created. It only reacts to tasks created from now on. A manual run applies it to records that are already there. You can use this for many things, including:
Filling a new field on every record in a database app.
Sending an email for records that already meet a condition.
Note:
A manual run has real effects. Test with
Simulated runfirst. Read Test automations →.Filters still apply. Only records that match the filter lead to a run.
Large runs count toward your usage. Every action in every run uses actions.
Before you start
Build the automation and check it with
Simulated run. You find it in the•••menu at the top of the editor.Make sure the trigger fits the records you want. Filters like
Has changedandHas changed todon't match in a manual run, because nothing changes. Use a filter on the current value, such asIs. Learn more in Filter automations by field changes →.Try one record first.
Run on records you choose
Open the automation in the editor.
Select
Manual run, or presscmd/ctrl+J.Next to
Run on, chooseSelected records, then pick records from the list. Each record shows where it's from, for exampleExpense in Accounting.Select
Start run. If you have unsaved changes, the button readsSave and start runand also saves them.
Run on all records of a database app
Open the automation in the editor and select
Manual run.Next to
Run on, choose one of these:Selected viewruns on the records in a view of the database.Number of recordsruns on the most recent records. Enter how many.All recordsruns on every record of the database.
Select
Start run. There's no extra confirmation, so check your choice first.
Check the result
Click ▷ next to Manual run (tooltip View all runs), or press cmd/ctrl + 1. Each record that matched the filter has its own run. Select a run to see its steps. Select Follow in the Runs panel to get a notification for every failed run. To stop runs that haven't finished, click ••• at the top right of the editor and select Cancel runs, then confirm. Learn more in Automation runs →.
If many runs are slow
When a lot of runs start at once, Tape may slow down automations across your organization for a while. Runs can show the status Throttled. Tape checks the load again shortly and runs waiting automations automatically. To spread the work out, read Update many records in batches →.
Other ways to reach existing records
Use a schedule with
Get viewandUpdate collectedto change many records in one run. Collection actions return at most 1,000 records.Use
When another automation callsand call the automation from another one.
Learn more
FAQs
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 questions? Find answers and get help from community experts in the Tape community →
