# How to introduce delays longer than 60 seconds?

**URL:** <https://forums.losant.com/t/how-to-introduce-delays-longer-than-60-seconds/111>\
**Category:** Help\
**Created:** [April 22, 2016, 10:58pm UTC](https://forums.losant.com/t/how-to-introduce-delays-longer-than-60-seconds/111 "2016-04-22T22:58:38Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Tim\_Mecklem](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.losant.com/tim_mecklem/32/117_2.png) [@Tim\_Mecklem](https://forums.losant.com/u/Tim_Mecklem)\
**Post date:** [April 22, 2016, 10:58pm UTC](https://forums.losant.com/t/how-to-introduce-delays-longer-than-60-seconds/111/1 "2016-04-22T22:58:38Z")

</div>

What’s a good way to have a longer delay than 60 seconds in a workflow? If I want 10 minutes, do I need 10 60 second delays?

---

<div class="post-metadata">

**Author:** ![Brandon\_Cannaday](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.losant.com/brandon_cannaday/32/14_2.png) [@Brandon\_Cannaday](https://forums.losant.com/u/Brandon_Cannaday)\
**Post date:** [April 22, 2016, 11:24pm UTC](https://forums.losant.com/t/how-to-introduce-delays-longer-than-60-seconds/111/2 "2016-04-22T23:24:28Z")

</div>

The maximum amount of time you can delay a single workflow execution, in total, is 60 seconds. Unfortunately adding more delays won’t get past this limitation as you will be attempting to cause a single workflow execution to exceed the 60 second limit.

A workaround is to use a timer that continually runs the workflow on some periodic interval - let’s say every 1 second. You can then continually check whether or not the current time is more than 60 seconds later than the start time.

You can use the [Store Value](https://docs.losant.com/workflows/data/store-value/) node to store the start time based on whatever triggers the 60 second timer. You can then use a [Conditional Node](https://docs.losant.com/workflows/logic/conditional/) to calculate the time difference and check if it exceeds 60 seconds.

I’ve attached a workflow that you can [import](https://docs.losant.com/workflows/overview/#import-export) that demonstrates this behavior. The virtual button stores the start time and the timer continually checks if it’s greater than 60 seconds. If it is, it logs a message with a debug node and clears the start time.

[60-second-timer.flow](https://forums.losant.com/uploads/short-url/sU3Bl39PBlf94UzcfqOixjcH9Fc.flow) (1.7 KB)
