Jrocks
Jrocks2w ago

Jrocks - If I add a sleep node with a wait time...

If I add a sleep node with a wait time of 1 year, does this mean it will use up 1 year of execution hours?
Solution:
@Jrocks, 1 year of wait time isn't ideal at all, could you please share your usecase for this? The hard timeout for a workflow's execution is 5 minutes, it will stop after it.
Jump to solution
6 Replies
Solution
Gaurav Chadha
Gaurav Chadha2w ago
@Jrocks, 1 year of wait time isn't ideal at all, could you please share your usecase for this? The hard timeout for a workflow's execution is 5 minutes, it will stop after it.
Jrocks
Jrocks2w ago
Automation for Birthday events. Monthly follow up and etc. So it does count as execution hours? So If I were to create a workflow with a node that has a 5-day wait (sleep), would that use 120 hours of my execution time for just one run?
Gaurav Chadha
Gaurav Chadha2w ago
yes, it is counted in execution hours.
Gaurav Chadha
Gaurav Chadha2w ago
Scheduled Cron Trigger – BuildShip
A unified resource to start building your backend with low-code. Dive into triggers, nodes, and step-by-step guidance to jumpstart your workflow creation.
Jrocks
Jrocks2w ago
Thanks for this @Gaurav Chadha . The cron job works, but a simple wait node would be a better solution for many of my use cases, especially for adjusting wait times dynamically. It’s a bit of a letdown to learn that a sleep node, which is just paused and not processing anything, counts toward execution hours. Being on the expert plan means a few workflow runs with a 5-day sleep node would use all my hours in an instance. I hope the BuildShip team can revisit this and consider making changes. It's not the end of the world, but I just wanted to give this feedback. I would love to hear @Harini's thoughts on this too 🙂
Harini
Harini2w ago
Hey @Jrocks sleep for 5 days doesn’t sound like an ideal setup - typically in workflows you wait for a few seconds or minutes to aggregate responses if needed. As Gaurav suggested - revisiting the logic of your workflow to use a scheduled cron instead would be better choice here. Lets chat on a call here to further understand your usecase and figure out best solution https://cal.com/shams