Workflow Not Triggered - 0 Steps Executed

One of my workflows was not properly triggered today (Feb 26, 2026, 05:23:04). The trigger fired, but the workflow shows "0 Steps Workflow" and "0 Free Tasks," meaning none of the steps executed.

Task History: https://connect.pabbly.com/task/history?filter_status=applied&filter_by_workflow_id=IjU3NjYwNTZiMDYzNTA0MzU1MjZkNTUzMTUxMzIi_pc#

The task shows "Success" status, which is misleading since nothing actually happened. This is not the first time I've run into reliability issues with Pabbly, and frankly, it's getting really frustrating. I'm running a business that depends on these workflows working correctly. When they silently fail like this, it costs me time and damages trust with the people I work with.

I've already handled this manually, so do not re-execute this task. What I need is a clear explanation of why this happened and, more importantly, a guarantee that this won't keep occurring.

This needs to be taken seriously.

Sven

Hey @sven-bo,

We have escalated this issue to our technical team for further review. Kindly allow us some time to investigate this.

We will get back to you with an update as soon as we receive it from our team.

Thank you for your patience and cooperation.

Hey @sven-bo,

Thank you for your patience.

This specific instance may have occurred due to the server downtime on that date, which likely prevented the workflow steps from executing even though the trigger was received. The issue is not occurring currently, and the services are functioning normally.

To resolve this, our team has re-executed the specific Task History, and it has executed successfully.

If you encounter any similar issues in the future, please let us know and we will be happy to assist you promptly.

Thanks for the update, Preeti.

Unfortunately, I explicitly stated in my original message: "I've already handled this manually, so do not re-execute this task."

By re-executing it, you've now sent a duplicate welcome email to my customer and created a duplicate database entry. So the "fix" has actually created a new problem for me...

Hey @sven-bo,

We sincerely apologize for what happened. We overlooked your instruction not to re-execute the task and unfortunately missed informing our team about it.

We truly understand the inconvenience this has caused, especially with the duplicate email and database entry, and we sincerely regret the mistake. We will take extra care to ensure such instructions are followed properly moving forward.

Thank you for your understanding, and once again, we apologize for the inconvenience caused.