Delay not working properly.

My workflow has a basic delay until step.

Whenever the workflow reaches to the delay step, it delays but does not execute the next steps, it just shows "Stopped" WITHOUT ANY MANUAL INTERVENTION.
This has been going since Jan 22, 2025 (IjU3NjUwNTZmMDYzMjA0MzA1MjY1NTUzMzUxMzU1MTYyNTQzNTBmMzci_pc).

Please tell me a fix for it ASAP.

Thanks
Regards
Manoj Goel

Hello @manojgoel,

The workflow is functioning correctly as per the configuration, and the delay step is working fine. However, we noticed an issue where the delay step is receiving a date that is prior to its execution time. For example, the delay step is executed on 5th February 2025 at 3:00 PM, but the date entered in it is 5th February 2025 at 10:00 AM. Since the time has already passed, the workflow gets paused at that step.

To resolve this, your workflow will need some adjustments. Could you please elaborate on the exact use case you're trying to achieve? This will help us guide you on how to resolve the issue.

It is clearly written beneath the Delay Date field in the Delay step. "Date should be (YYYY-MM-DD HH:mm:ss) format like 2021-12-15 16:25:30 and it should be in UTC+0 Time Zone only. You can convert any time in a UTC format here."
Please tell if I input the time in my local time will the delay work properly then?

Hello @manojgoel,

Yes, the delay will work in the UTC timezone.

"Date should be (YYYY-MM-DD HH:mm:ss) format like 2021-12-15 16:25:30 and it should be in UTC+0 Time Zone only. You can convert any time in a UTC format here."

No, if you enter the time as per your Local time which seems to be Asia/Kolkata, the delay step won't get delayed as required.

Please tell if I input the time in my local time will the delay work properly then?

Please let us the below details so we can suggest to resolve this issue.

1. The date from the trigger is getting received as per which timezone Asia/Kolkata or UTC?
2. Your exact use case that you're trying to achieve.

1. UTC
2. Booking Reminder

Hello @manojgoel,

Could you elaborate on the use case that you are trying to achieve via the already-added actions? This will help us better understand what each step does, if you add a screen recording or screenshots it would be better.

Hi Preeti! I'm facing the same issue: The delay step pauses the workflow when the time has already passed. In any other tool like Make and Zapier their are options to handle prior dates (SS Attached). This is a very basic feature.

My use case: I'm trying to automate reminders for my webinars with following WhatsApp messages using Interakt:
1. Registration Confirmation
2. 1 Day To Go ( Webinar Date minus 24 hrs)
3. 1 Hr To Go (Webinar Date minus 1 hr)
4. We're Live (Webinar Date minus 10 mins)

I've sequenced them using a mix of "Date Formater's Subtract option" & "Delay option" by Subtracting required days from Webinar Date.

The problem is that some users register on the day of the webinar hence for them "1 Day To Go" message is not relevant. Hence that should be skipped for them (tried by Routing, but failed because of prior delay date).

Also, in a simple delay workflow (without Routing) the flow stops for all users (who register on the webinar day) after step 1 because of the prior delay date. Please help resolve this asap.

Your concern is being addressed here:
https://forum.pabbly.com/threads/pabbly-delay-stops-workflow-if-the-date-has-passed-already.28675/