Tip: Start with the run history. Click ▷ next to Manual run in the automation editor to see every run, its date, and its status. A run that appears there did start. Learn more about Automation runs →
If you can't find a run for the record you expected, work through the situations below from top to bottom.
If the automation is paused
A paused automation doesn't start on its trigger. To turn it on:
Open the automation. Click the automations icon at the top right of the database app (
Create and view automations), then select the automation.Select the status button in the editor. It shows
Paused, and one click switches it toActive.Select
Save changes.
New automations you create in the editor are Active right away. Automations created through the API start Paused, so activate them first. Learn more about Active, paused, and broken automations →
If the automation is marked as broken
The status chip in the editor turns red and shows Broken instead of Active or Paused, for example when a field, app, person, or option the automation uses no longer exists. A broken automation doesn't start on its trigger.
To fix it, open each step and check the fields, apps, and people it uses. Select a new one wherever the old one is gone, then select Save changes.
If the trigger doesn't fire
Check that the trigger matches what you did:
When a record is createdruns only for new records. It doesn't run for records that already exist. To run an automation on existing records, useManual run. Learn more about running automations on existing records →When a record is updatedruns when a field changes. Open the trigger and check the fields underFIELDS. If it's set to specific fields, a change to any other field doesn't start the run. If no field is selected, the trigger showsSelect a fieldin red and the automation isBroken. It doesn't run until you select at least one field, orAny field, and save.When a date field arrivesandOn a scheduled time or intervalstart on their own at a set time. Check the date, the time, and the time zone. A time that looks wrong is often a time zone issue. Learn more about Dates or times are off →A change made by another automation or by an API request may not start this one. See "If another automation made the change" below.
If the filter stops the run
A filter decides which records continue. If a record doesn't meet the conditions, the actions don't run.
A simulated run skips the filter and doesn't change any data. To test the filter, use Manual run on a test record. Only matching records start a run. If a record doesn't match the filter, no run appears in the history. Learn more about My filter doesn't match →
If another automation made the change
When one automation changes a record, the change can start a second automation, but not always. The action's settings decide this:
Select the
•••of the action that creates or updates the record.Check
Trigger automations. When it's on, the action can start other automations. It's off by default.Check
Silent. A silent change is made without notifying people.Silentonly turns off notifications. It doesn't decide whether other automations start.
If the run starts but stops early
Open the run and look at its steps. A step that failed shows its error message, and the steps after it don't run. To find runs quickly, open the Runs view of the Automation Center and filter by Status: Scheduled, Running, Success, Throttled, Failed, or Cancelled.
Failed: read the error message of the failed step. Learn more about Common automation errors →ThrottledorScheduled: the run is waiting. Learn more about My automations are delayed →Cancelled: the run was stopped, for example withCancel runsin the editor.
To get a message whenever a run fails, select Follow in the Runs panel. Its tooltip reads "Receive notifications for all failed runs".
Test the automation
To find out where it stops, test it step by step:
Select
Simulated runto see the steps without side effects. It skips the filter and doesn't change any data.Select
Manual runto run it once on a record. This makes real changes, so use a record meant for testing.
Tip: Still having trouble? Ask in the Tape community.
Learn more
FAQs
Why did my automation work yesterday but not today?
Why did my automation work yesterday but not today?
If an automation suddenly stops running, it could be because:
It was paused. Check the status button in the editor.
A field, app, or person it uses was deleted or removed.
Your organization's automations are throttled because they used a lot of capacity in a short time. Learn more about delayed automations →
Why doesn't my automation run for records that already exist?
Why doesn't my automation run for records that already exist?
Triggers react to new events, not to old records. Use Manual run to run the automation on existing records.
Can I get a message when an automation fails?
Can I get a message when an automation fails?
Yes! Open the automation, click ▷ next to Manual run, then select Follow. You'll get notifications for all failed runs of that automation.
Does a paused automation lose its settings?
Does a paused automation lose its settings?
No. Switch it back to Active and it uses the same settings as before. Events that happened while it was paused don't start it later.
Still have questions? Find answers and get help from community experts in the Tape community →
