Skip to main content

My automations are delayed

Learn why automation runs wait, how throttling works for your whole organization, and what to do so scheduled and busy automations start on time again.

Written by Leo

Tip: Check the status of the run. Select Runs in the Automation Center, then filter by Status. A run that waits shows as Throttled or Scheduled. Learn more about Automation runs →

Opening the Status filter in Runs in the Automation Center, which lists Scheduled, Running, Success, Throttled, Failed, and Cancelled, and pointing at Throttled

If your runs show as Throttled

Tape may throttle an organization whose automations cause an unusually high load in a short time, for example many runs or many filter checks at once. Throttling has no fixed duration. It ends on its own once your organization's automation load drops. During that time, runs can start later than usual.

What to know:

  • Throttling affects the whole organization. All workspaces and apps in your organization slow down, not only the automation that used the most actions.

  • A Throttled status marks it. While your organization is throttled, waiting runs show Throttled in Runs.

  • It's temporary. You don't need to turn anything off. Throttled runs start on their own once throttling lifts.

  • Admins can get notified. Organization owners and admins can send a webhook to another tool when the organization is throttled. In Runs, click ••• (tooltip Webhook, export and more), select Webhook notifications → Add webhook, enter a URL, and choose Organization throttled.

In Runs in the Automation Center, opening ••• and Webhook notifications, selecting Add webhook, typing <a href="https://hooks.acme.com/tape" rel="nofollow noopener noreferrer" target="_blank">https://hooks.acme.com/tape</a>, then opening the event menu Run failed and pointing to Organization throttled

Find what uses so many actions

Throttling usually starts when one automation causes a lot of activity at once. Common causes are:

  • A loop over many records. A loop repeats its steps for every record, so it can use many actions.

  • An import or a bulk update that changes many records at the same time, and each change starts an automation.

  • Several scheduled automations that start at the same time, or one that calls another automation for many records at once.

To find out which automation is behind it:

  1. Select Automations in the sidebar to open the Automation Center. You see it if you're an organization owner or admin and a workspace admin in at least one workspace.

  2. Check Used actions and Available actions for your usage. Learn more about Automation usage →

  3. Open Runs, filter by App or Automation, and look for an automation with many runs at the same time.

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

Spread the work out

If a big job causes throttling, give Tape smaller pieces of work:

If a single run takes too long

A single run can take at most three minutes and use at most 1,000 actions. If a run goes over a limit, it fails with an error message instead of waiting. Learn more about Common automation errors → and Automation limits and throttling →

If a scheduled automation starts late

A scheduled automation doesn't start at the exact minute. Tape checks for due automations at regular intervals, so a run can start a few minutes after the set time, even when your organization isn't throttled. Also check the time zone of the automation. Learn more about Dates or times are off →

If a run seems stuck

A run that shows Running for a long time may be waiting on a slow step, for example an HTTP request to another service. A run that takes longer than three minutes fails. To stop runs you no longer need, open the automation, click ••• (tooltip Undo, delete and more), and select Cancel runs. Tape asks whether to cancel all runs of this automation. Confirm with Cancel runs.

Opening ••• in the header of the Expense approval editor, selecting Cancel runs, which asks Cancel runs? Are you sure you want to cancel all runs of this automation?, and closing the dialog with Cancel

Tip: Still having trouble? Ask in the Tape community and include the automation name and the time of the delay.

Learn more

FAQs

How long does throttling last?

There's no fixed duration. Throttling ends on its own as soon as your organization's automation load drops, and waiting runs then start automatically.

Does throttling only affect the automation that caused it?

No. Throttling applies to your whole organization, so every automation can be delayed for a while.

Can I get more actions so I'm not throttled?

No, throttling looks at the load in a short time, not at your monthly actions. To avoid it, spread the work out. The number of automation actions per month depends on your plan. See the limits for your plan on our pricing page.

Will I lose runs while my organization is throttled?

No. Runs are queued and run after throttling lifts. Check the Runs list afterwards. If a run shows Failed, open it to read the error.

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

Did this answer your question?