Skip to main content

Active, paused, and broken automations

An automation is active, paused, or broken. Learn what each status means, how to switch between active and paused, and how to fix a broken automation.

Written by Leo

The status of an automation tells you whether it reacts to its trigger. You can use the status for many things, including:

  • Pausing an automation while you change it.

  • Finding automations that stopped working because a field or app was deleted.

Selecting the status Paused below the automation name Expense approval switches it to Active, then the pointer moves to Save changes

Note:

  • New automations are active right away. Use Paused while you build if you don't want it to start yet.

  • A paused automation doesn't start on its trigger. You can still run it by hand with Manual run.

Active

An Active automation starts whenever its trigger happens. The status below the automation's name in the editor shows Active, and so does the list of automations in the Automation Center →.

Paused

A Paused automation doesn't start on its trigger. Changes made while the automation is paused don't start it later, even after you activate it again.

To pause or activate an automation:

  1. Open the automation in the Automation editor →.

  2. Select the status below the automation's name. It switches between Active and Paused.

  3. Select Save changes. The new status applies once you save.

You can also pause or activate an automation in the Automation Center: click ••• on its card, then select Pause or Activate. This applies right away.

In the Automation Center, opening Accounting and Expenses, then the ••• menu on the card of the paused Expense approval automation, and pointing to Activate

Broken

An automation is broken when it can't run because something it needs is gone. Examples are a deleted field, a deleted app, or a deleted view. The status below the name shows Broken, and you can't switch it. In the Automation Center, the card of a broken automation shows Broken.

A new automation with the status Broken below its name, because the trigger When a record is updated shows Select a field in red

To fix a broken automation:

  1. Open the automation in the editor.

  2. Find the step that refers to the missing item. The editor marks the title of that step, and the missing field, app, or person, in red.

  3. Select a field, app, view, or person that exists, or remove the step.

  4. Select Save changes. The status changes back to Active once nothing is missing.

In a new, unsaved Tasks automation with the status Broken, opening the red Select a field in the trigger When a record is updated and selecting Status, so the status changes to Active

A broken automation can't be started with Manual run. Tape shows the message Trigger runs manually not possible because of broken automation.

What happens when a run fails

A failed run is a result of one run. It doesn't change the status of the automation. To see why a run failed, click ▷ next to Manual run in the editor (tooltip View all runs) and open the run. To carry on after a failed step, select Continue on error in the action's menu. Learn more in Handle errors in automations →.

Clicking the runs button next to Manual run to open the Runs panel, opening a failed run, and expanding the failed step Create a record to read its error

Status errors

Learn more

FAQs

Does pausing an automation delete its runs?

No, the runs stay in the run history.

Can I run a paused automation?

Yes! Manual run works on a paused automation. It has real effects, so be careful.

Why did my automation become broken?

Something it uses is gone, for example a deleted field, app, or view. Open the automation, look for the steps marked in red, and choose an item that exists.

Is a deactivated action the same as a paused automation?

No. Paused stops the whole automation. Deactivate skips one action inside an automation.

Are you a developer using the Tape API for automations?

The automation API has its own documentation for developers. Full reference: Manage automations in the developer docs →

Still have questions? Find answers and get help from community experts in the Tape community →

Did this answer your question?