Tape applies limits to every automation run (a run is one execution of an automation) to protect computing power and time. Throttling is a temporary slowdown that Tape can apply to a whole organization. Limits are meant to keep automations fast and reliable for everyone.
You can use this page for many things, including:
Finding out why a long run stopped before the end.
Planning how to split a large update into smaller runs.
Note:
A run that reaches the time, action, or memory limit fails. The run shows an error message.
One limit doesn't fail the run. A collecting action cuts off its list at 1,000 records without an error.
A used-up email quota fails the email step. The run fails too, unless the step has
Continue on errorturned on.
Limits of a single run
Run time: A run can last up to three minutes. After that, Tape stops it.
Actions per run: A run can use up to 1,000 actions.
Memory and computing power: Memory and CPU limits apply to every run.
Waiting for other services: Time a run spends waiting for another service to answer, for example during an HTTP request, counts toward the three-minute limit.
Runs at the same time: Tape limits how many automation runs of your organization run at the same time, so runs may wait until others are done.
Records per collecting action: A single action that collects records returns at most 1,000. Tape cuts off anything beyond that without a warning, even if you set a higher number in
Limit results. Learn more about collected records →Emails: Emails sent through Tape's own sending account share your organization's 24-hour sending quota, which counts the emails of the last 24 hours. When it's used up, the
Send emailstep fails with an error until older emails drop out of that window. Emails sent through your own email account don't count toward this quota. Learn more about sending emails →Nesting: You can put loops and conditions inside each other. Keep the nesting shallow so the automation stays easy to follow and test.
Webhook data: The data a webhook receives has a size limit. Larger requests are rejected, and the automation doesn't run. To send files, post them as
multipart/form-data.Delay:
Delay executionwaits for15 seconds,30 seconds,45 seconds, or60 seconds. The default is30 seconds. The waiting time counts toward the three-minute limit.
Limits for an app
Automations per app: An app can have up to 500 saved automations. After that, you can't save another one until you delete one.
Name of an automation: 1 to 5,000 characters.
Throttling
Tape can throttle an organization whose automations create an unusually high load in a short time, for example many runs or many records checked by triggers at once. While throttling applies:
It affects the whole organization, not a single automation. It leads to temporary delays.
It ends on its own once your organization's automation load drops below the limit. Tape checks the load again shortly and runs waiting automations automatically.
Runs that are waiting to start show an orange
Throttledstatus instead ofScheduled, in the runs of an automation and in the runs overview. This applies to automations with any trigger, not only to automations on a schedule.
To see throttled runs, go to Automations → Runs, open the filter for Status, and select Throttled. Learn more about delayed automations →
To get notified in another tool when your organization is throttled, open Runs in the Automation Center, click •••, and select Webhook notifications. Select Add webhook, enter a URL, and choose Organization throttled. Only organization owners and admins see ••• there.
What to do when you reach a limit
Split the work. Let one automation start others with
Call automation, each with a smaller list. Learn more about batches →Use fewer actions. Filter records before you collect them, and use actions for collected records instead of a loop where one step is enough.
Avoid heavy calculations on large lists in a script.
Spread out emails. Send them over several days or in batches. Learn more about bulk emails →
Let's look at an example
Let's say your real estate team wants to update 5,000 properties in one go. A single run can't handle all of them. Here's how to split the work:
Create an automation with the trigger
On a scheduled time or interval, set to run every hour.Select
Add action→Get viewand choose a view that only shows properties that aren't updated yet.Click
•••on the action, switch onLimit results, and set a small number, for example 200.Add
Update collectedto change the collected properties.Select
Save changes.
Each hour, the next 200 properties are updated, so every run stays small.
Limit errors
A run stops after three minutes. The run shows "Action execution failed due to timeout. Avoid long runtimes for your workflow." Reduce the work per run, or split it into batches.
A run fails because it used too many actions. The run shows "Too many actions used" with the number of actions. A run can use up to 1,000 actions. Collect fewer records or avoid loops over long lists.
A run fails because of memory or computing power. The run shows "Action execution failed due to resource limit exceeded." Avoid heavy calculations on large lists.
A list is shorter than expected. The 1,000-record limit applies. Add filters or work in batches.
Emails aren't sent. The 24-hour quota of Tape's sending account is used up. The
Send emailstep fails until older emails drop out of the 24-hour window. Send fewer emails, for example one summary email instead of one per record. Learn more about My automation emails don't arrive →A new automation can't be saved. The app already has 500 saved automations. Delete one you don't need.
Learn more
FAQs
Can I raise a limit?
Can I raise a limit?
No, the limits of a single run are the same on all plans. Automations are available on all plans: Free, Plus, and Premium. The number of automation actions per month depends on your plan. See the limits for your plan on our pricing page.
Why did my run stop after three minutes?
Why did my run stop after three minutes?
A run can last up to three minutes. Split the work into smaller runs.
Is the email quota per automation or for the whole organization?
Is the email quota per automation or for the whole organization?
For the whole organization. All automations that send through Tape's own sending account share one 24-hour quota. Emails sent through your own email account don't count toward it.
Do I lose runs when my organization is throttled?
Do I lose runs when my organization is throttled?
No. Runs wait and start automatically once throttling ends. They aren't lost.
Does Tape warn me when a list is cut off at 1,000 records?
Does Tape warn me when a list is cut off at 1,000 records?
No. The cut-off happens silently when the run executes. Check the number of records in your collecting action if the list matters.
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: Limitations and throttling in the developer docs →
Still have questions? Find answers and get help from community experts in the Tape community →
