flow stopped after 3 minutes of delay

[abhishekg]

Your Workflow URL

https://connect.pabbly.com/workflow/mapping/IjU3NjcwNTZkMDYzNTA0M2Q1MjZiNTUzNTUxM2Ii_pc

Your Task History ID

IjU3NjUwNTY0MDYzMzA0MzU1MjY4NTUzYzUxMzI1MTY1NTQzNjBmMzUi_pc

Consent to Access & Modify

I don't authorize Pabbly Support to log in to my account.

there is 3 minutes of delay in the flow, however the execution did not continue after delay

 

[ArshilAhmad]

Hi @abhishekg,

Based on your Task History, we can see that the task was stopped manually. Did you, by any chance, stop the execution of this task?

Thanks & Regards,
Arshil Ahmad
Customer Support Associate
Pabbly.com
Rate your support

 

[abhishekg]

No team, we did not touch this at all, I can confirm you on this.

 

[Hrishabh.pabbly]

Hi @abhishekg,

Thank you for confirming.

We have escalated this issue to our technical team for further investigation. They will look into why the workflow did not continue after the 3-minute delay, even though no manual intervention occurred.

We will keep you updated on the progress and notify you once a resolution is available.

Thank you for your patience.

 

[Hrishabh.pabbly]

Hi @abhishekg,

Thank you for your patience.

Upon further investigation, we found that there was a temporary server downtime during the same time window when the 3-minute delay step was scheduled to resume execution.

Due to this brief downtime, the workflow execution did not automatically continue after the delay step, even though it was not manually stopped from your end. We sincerely apologize for the inconvenience caused.

Our system is now stable, and such cases are rare. However, if you notice any similar behavior in the future, please feel free to share the Task History ID with us so we can review it immediately.

Thank you for your understanding.