Delay execution is an action that pauses the run for a short, fixed time before it goes on with the next action (the pause only affects this run, not other runs of the automation). It's meant to help you give a step time to finish before the next one depends on it.
You can use this action for many things, including:
Waiting a few seconds before an action starts another automation, so that the first change has time to complete.
Waiting before a record is deleted, to leave time for a last check.
Note:
A delay lasts seconds, not hours or days. You can pick 15, 30, 45, or 60 seconds. To wait for a date or run something later, use a trigger instead.
The wait counts toward the run time. A run can take up to three minutes in total, so several long delays in a row can use it up.
A delay can use an action. The wait itself doesn't count. In automations that run on a record, Tape reloads the record after the wait, which uses one action. A run can use up to 1,000 actions.
Who can use the Delay execution action?
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.
To add or change this action, you need to be a
Workspace adminof the workspace the app is in. App permissions alone aren't enough.
Add the Delay execution action
To pause an automation:
Open the app and click the automations icon at the top right (
Create and view automations).Open an automation, or select
New automationand choose a trigger.Select
Add action→Delay execution. In the list, its description readsDelay execution of actions.Select the time, which starts as
30 seconds, and choose a different one.Select
Save changes.
Delay execution settings
The action reads Delay execution by waiting for 30 seconds. You can change the time:
15 secondspauses the run for 15 seconds.30 secondspauses the run for 30 seconds. This is the starting value.45 secondspauses the run for 45 seconds.60 secondspauses the run for 60 seconds.
No other values are available. To wait longer, add several delays, but keep the three-minute run limit in mind. The action menu ••• has Settings, Continue on error, Deactivate, Turn into, Duplicate, and Remove. Learn more about action settings →
Let's look at an example
Let's say your project team creates a project record from a request, and a second automation then sets up the first tasks. Here's how to give the first step time:
Set the trigger to
When a record is createdin theRequestsapp.Select
Add action→Create recordand create the project.Select
Add action→Delay executionand choose15 seconds.Select
Add action→Call automationand choose the automation that creates the tasks.Select
Save changes.
The next time a request comes in, the run creates the project, waits 15 seconds, and then calls the second automation.
Delay execution and limits
Each delay takes the full time you chose. The run keeps running during the wait.
After the wait, Tape reloads the current record, so later actions use its latest values, including changes that other automations made in the meantime.
A run can take up to three minutes. If a delay pushes the run over, the run fails with a timeout message.
Under heavy use, runs can take longer to start. Learn more about delayed automations →
Delay execution errors
If the run fails because of a timeout, the total of all delays and actions went over three minutes. Remove or shorten delays, or split the work.
If a later action still can't find what it needs after the delay, the step the delay was meant to wait for probably failed. Open the run and check that step. Learn more about error handling →
Test, pause, or edit the Delay execution action
Manual runruns the automation once. UnderRun on, select the records, then selectSave and start run. The delay takes the real time.A simulated run skips the delay and doesn't wait.
To skip the delay without removing it, select
Deactivatein its menu.To change the time, open the automation, select the time on the action, choose a new one, then select
Save changes.
Learn more
FAQs
Can I wait for more than 60 seconds?
Can I wait for more than 60 seconds?
Not with a single delay. You can choose 15, 30, 45, or 60 seconds. You can add several delays in a row, but a run can take up to three minutes in total.
Can I wait until a date or time?
Can I wait until a date or time?
No. Delay execution only waits for seconds. To start an automation at a date, use When a date field arrives. To run on a schedule, use On a scheduled time or interval.
Can I use a variable for the waiting time?
Can I use a variable for the waiting time?
No. The time is one of the four fixed values.
Why did my run take so long?
Why did my run take so long?
Delays add their full time to the run. Check the steps of the run, and remove any delay you don't need.
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: delay in the developer docs →
Still have questions? Find answers and get help from community experts in the Tape community →
