Skip to main content

My automation runs in a loop

Stop an automation that keeps starting itself or another automation. Find the loop in your run history, then break it with filters or settings.

Written by Leo

Tip: Stop it first. Pause the automation so no new runs start. Open it and select the status button so it shows Paused, then select Save changes. You can also select Pause in the ••• menu of its card in the Automation Center. To stop runs that are already waiting, click ••• (tooltip Undo, delete and more) in the editor and select Cancel runs.

A loop happens when a change made by an automation starts an automation again. A change by an action can only start automations if Trigger automations is on in that action. It's off when you add the action. For example, an automation that runs When a record is updated and updates the same record with Trigger automations on can start itself. Two automations can start each other in the same way.

The menu of an Update the current record action opens with its ••• button. The pointer rests on the Trigger automations switch, which is off.

If an automation starts itself

Open the automation and check the trigger and its actions. Both cases below only loop if Trigger automations is on in the action:

  • When a record is updated and an Update the current record action in the same automation start the trigger again.

  • When a record is created and a Create record action in the same database app create a new record, which starts the trigger again.

How to fix it

Use one of these options, or combine them:

  1. Limit the trigger. Select the fields the trigger watches, so a change to other fields doesn't start the run. Don't select the fields that the actions set.

  2. Add a filter. Select Add filter, then add a condition that is no longer true after the change. For example, Status Has changed to "Submitted" runs only once, because the action changes the status to "In review".

  3. Switch off Trigger automations. Select the ••• of the action that changes the record, then switch off Trigger automations. The change then doesn't start other automations. Learn more about Action settings →

    The menu of an action with Trigger automations marked. The switch is off, so the change doesn't start other automations.
  4. Write to another database app. Create the record in another database, or update a field that the trigger doesn't watch.

If two automations start each other

Automation A changes a record, which starts automation B, which changes the record again and starts A. To find this:

  1. Open Runs in the Automation Center, or click ▷ next to Manual run in each automation.

  2. In the Automation Center, filter by App and look for two automations with runs one after another in a short time.

  3. Open a run and check which step changed the record.

Opening Runs in the Automation Center, filtering App by Expenses so only runs of Expense approval are listed, and expanding the newest run to see its steps

How to fix it

Apply the same options as above to one or both automations. Switch off Trigger automations on the action that starts the other one. If one automation should start the other on purpose, use the trigger When another automation calls instead of relying on a record change. Learn more about Call automation → Calls can loop too: Tape doesn't stop an automation that calls another one that calls it back.

What a loop does

A loop can cause a lot of activity quickly, and Tape can throttle your organization until the load drops. All automations in your organization are then delayed. Each run also has limits of three minutes and 1,000 actions. Learn more about My automations are delayed →

What to know about the setting:

  • Trigger automations decides whether a change can start automations in Tape, including the same automation. It's off when you add the action. A switch in the menu shows whether it's on.

  • Trigger webhooks decides whether the change sends a webhook to other systems. A webhook that changes the record again can create a loop too.

  • Silent makes the change without notifications. It doesn't stop a change from starting other automations.

Prevent loops

Tip: Still having trouble? Ask in the Tape community and include the names of the automations involved.

Learn more

FAQs

How do I know an automation is in a loop?

If an automation is in a loop, you'll see many runs for the same record in a short time in Runs. Tape doesn't detect loops on its own. If a loop causes a lot of activity, Tape throttles your organization.

Is a loop the same as Loop actions?

No. Loop actions is an action that repeats steps for each record of a list, on purpose. This page is about automations that start each other by accident. Learn more about Loop actions →

Can I let one automation start another on purpose?

Yes! Use Trigger automations on the action, or call the other automation with Call automation. Add a filter so the second automation doesn't change the record that starts the first one.

Will pausing the automation delete its runs?

No. Pausing stops new runs. Your run history stays in Runs.

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

Did this answer your question?