Experiencing Longer Delays

Hello, welcome to the callin.io community! Could you please elaborate further?

{116300EB-397D-4DE6-9393-B2566205B0E9}967×673 37.3 KB

Give this a try. Configure the repeats for the desired number of times, with a 5-minute delay between each. Once it finishes, the process will proceed.

I'm looking to implement a delay of 4 hours and then another 2 days before executing a subsequent scenario in my router. I attempted to use the sleep module, but unfortunately, its maximum duration is only 5 minutes. I reviewed the provided link and experimented with using a cron job; however, the error I previously shared continues to persist.

I believe I might utilize this. It's so straightforward to grasp compared to the YouTube videos I've seen, haha. Does it perform this effectively on a daily basis?

I would suggest splitting your scenario into two separate ones.

At the conclusion of the first scenario, store the data required for subsequent steps in a Data Store. Include a timestamp and another field (e.g., merged in this example) to indicate if it has already been processed by the 4-hour check.

The second scenario would utilize the Search Records module from the Data Store with the following criteria:

{AA8821C1-D93D-428C-ACF1-17DFD7203DE6}467×848 35.8 KB

If the processing for the 4-hour and 2-day intervals differs, simply use a router to distinguish between them, applying the same filter as the Search Records module. After the 4-hour delay, reset the date field to the current time and set the merged field to true. For the 2-day delay, remove the record from the store as the final step.

Implementing a lengthy delay within a single scenario is not advisable. You would face significant delays in verifying if your modifications were successful. It's more efficient to place all necessary data into a Data Store queue and have a separate scenario periodically check for records to process after your specified waiting period.

I was wondering if I have a delay in a router, does that mean it will wait to finish the timer before running the whole scenario again?

If you encounter a delay within a router node, the entire workflow will pause until that delay completes. However, multiple instances of the workflow can run concurrently, unless you have activated Sequential Processing for the scenario.

So, it's more convenient to break it into pieces rather than keeping it in the same flow.

In your situation, absolutely. If you were simply looking for a 20 or 30-minute delay, it would likely be acceptable to implement the delay within a single scenario. However, even then, it can be inconvenient when you are making or testing modifications. For delays spanning hours and days, it is significantly more advantageous to divide your task into two parts.

And actually, you just reminded me, you can’t delay beyond 40 minutes anyway, due to the scenario execution time limit.

I attempted these steps, but unfortunately, it didn't work for my outbound call (callin.io calling). I believe the first image you shared is much better, easier, and functional. Does it have a limit?

Also, is the Initial Value in Repeater set to 1?

Yes, the initial value is 1. However, I believe callin.io caps your total scenario execution time at 40 minutes, which is likely your limitation.

It should function correctly. Did the scenario execute and store the data record?

Please provide the rewritten markdown content; it should be in markdown format.

So the repeater isn't very useful when you need hours and days, huh.

Let me check it again one more time.

I attempted to implement a 4-hour delay, but it doesn't seem to be functioning. Could you please review it to see if I've configured something incorrectly?

image408×560 27.4 KB

image406×572 26.3 KB

image401×270 12.6 KB

image1205×462 50.3 KB