Hello, I’m new to make.com and need help setting my delay to longer than 5 minutes (sleep) module. I tried to cronjob that I watch on YouTube but I keep getting this error. Please see the photo for reference
Youtube reference
Hello @David_Balan, welcome to the make community can you explain more?
Try this. Set the repeats to however many times you want it to repeat 5min wait. Then once it’s done, it’ll continue.
2 Likes
I’m planning to have 4hours delay and another 2 days before running the other scenario in my router. I tried to use the sleep module but unfortunately it only last 5 minutes. I’ve watched the link i’ve posted and tried to use the cron job but unfortunately the error i posted keep bugging me.
I think I might use this. This is so basic to understand than the video I’ve watched in youtube lol. Does in days work this well?
I’d probably try splitting your scenario into 2 separate scenarios.
At the end of the 1st scenario, place your data needed for later steps into a Data Store along with the timestamp, and probably another column to determine if it was already processed by the 4 hour check (merged in this example)
2nd scenario is Search Records module of Data Store, with this criteria:
If the processing/automation for 4 hour and 2 day is different, just have a router that determines which is which, using the same filter as the Search Records module. At the end of the 4 hour delay, reset the date field to now + set the merged field to true. At the end of the 2 day delay, delete the record from the store as the last module.
Having a long delay in a single scenario is quite bad. You’ll be mightily frustrated having to wait hours/days to see if your changes worked. Better to just deposit all needed data into a Data Store queue and let another scenario check periodically for records to process after your desired wait time.
1 Like
I’ve wonder if I have the delay in router does it mean it will wait to finish the timer before running again the whole scenario?
If you have a delay in router, the whole scenario is halted until the delay has run its course. Multiple executions can be happening at the same time though, unless you enabled Sequential Processing on the scenario.
1 Like
So its better to break it to pieces than having it in the same flow which is more convenient.
In your case, definitely. If you were just wanting a 20 or 30min delay, it’d probably be OK to delay it within a single scenario, although still, it’s annoying if you’re making/testing changes. But hours and days, it’s really better to split your task in 2.
1 Like
And actually you just reminded me, you can’t delay beyond 40min anyway, because of the scenario execution time limit.
1 Like
I tried these steps but unfortunately, it didn’t go thru in my outbound call (vapi calling). I think the 1st image you sent is way better easier and working. Does it have a limit?
Also does the Initial Value in Repeater = 1?
Yes initial value is 1. But I believe you’re capped at 40min total execution time by Make on a scenario, so that’s probably your limit.
It should work, did the scenario execute the data stored record?
So the repeater is not useful at all when you need hours and days huh.
Let me check it again 1 more time
You should see an output bundle for each record that matched:
Also:
merge filter should be a boolean operator
Do you mind if request for the blueprint you had in that particular automation? So i could try it on my end as well?
Oh I see another issue too, in this module that creates the record, for testing, you want to set it to -4 hours
Normally you want to set this to just now but for testing, I think you were trying to make the difference in time less.
blueprint (19).json (6.0 KB)
blueprint (20).json (5.9 KB)