Delay after queue not working properly.

[opti-biz]

Hello @Preeti Paryani ,
I have same issue: the delay step has stopped the workflow which is now stuck.
- delay step started on 17/4 until 24/04
- it simply stopped there and did not resume on 24/04.

 

[Preeti Paryani]

Hello @opti-biz,

Could you please provide us with the Workflow URL where you are facing this issue? This will help us investigate the problem more effectively and assist you accordingly.

 

[opti-biz]

@Preeti Paryani Hello, I am having the same issue.

The workflow stopped at the delay step, and now, the delay date is passed, but the workflow has not resumed.
Can you please check?

 

[opti-biz]

Hello @opti-biz,

Could you please provide us with the Workflow URL where you are facing this issue? This will help us investigate the problem more effectively and assist you accordingly.

Hello, here is the workflow id: IjU3NjMwNTZiMDYzMzA0M2Q1MjY0NTUzNSI_3D_pc

Thank you
Fanny

 

[Preeti Paryani]

Hello @opti-biz,

Upon reviewing the workflow history, we observed that it has been working as expected. Please refer to the attached image for more details.

 

[opti-biz]

Hello @opti-biz,

Upon reviewing the workflow history, we observed that it has been working as expected. Please refer to the attached image for more details.

View attachment 56207

Hello @Preeti Paryani

You did not look at the right instance; you should check
Executed at

Apr 17, 2025 13:28:54, (UTC+02:00) Europe/Madrid​

 

[Resham]

Hello,
Greetings!
We’ve checked and found that the issue occurred due to a temporary server downtime. In case you face any similar issues again, please don’t hesitate to let us know—we’ll be happy to assist you promptly.

 

[opti-biz]

Hello,
same error occured again !

Pabbly

connect.pabbly.com

the workflow is stuck in the delay step, and there is no way to unblock it. Please help, this is crucial for operations in the company

 

[Preeti Paryani]

Hello @opti-biz,

We would like to inform you that our team has implemented some changes specifically related to the Task History section.

The task in question appears to have been processed during the update window roughly between 11:30 AM and 01:00 PM, which may have affected how it is displayed.

We recommend monitoring the workflow again from the Task History section going forward. The changes made during that period may have impacted the visibility or status of tasks, but subsequent executions should now reflect correctly going forward.

Please check the connected applications as well to confirm if the expected actions were completed. Let us know if you observe any further discrepancies.

 

[opti-biz]

@Preeti Paryani Could you specify which timezone should I consider for the update window you mentioned ?

The task in question was expected to execute at 7:45 UTC

 

[Preeti Paryani]

Hello @opti-biz,

The timezone I mentioned was IST.