Debugging in Pabbly Connect is a pain (the bad Task History design)

[apps]

Your Workflow URL

IjU3NjEwNTY5MDYzNjA0M2M1MjZlNTUzMyI_3D_pc

Your Task History ID

IjU3NjUwNTZhMDYzNjA0MzQ1MjZjNTUzNzUxMzY1MTYyNTQzNzBmMzQi_pc

Consent to Access & Modify

I authorize Pabbly Support to log in to my account and make changes to the specified workflow for troubleshooting.

Hi,

Please see these two videos:
- https://share.zight.com/4guEob5P
- https://share.zight.com/7KurOdyE

I simply can't figure out how to read the task history - it is super cumbersome to do debugging. Infomration is missing and listed in an illogical way imho.

Eg.:
- Have router options show in the correct order (seems random)
- Indicate visually if a router conditions is false or true
- Indicate the level of each router
- Indicate which router any sub-actions run from.

Also made two others feature requests related to debugging here but they are some different aspects.
- https://roadmap.pabbly.com/p/essential-debugging-feature-automatically-identify-webhook-sources
- https://roadmap.pabbly.com/p/automated-account-wide-automation-map

In general, when working with Pabbly Connect, one of the most time-consuming things is debugging. And it's also part of those things that take up a lot of your staff's time. So if you could improve these features, I'm sure that you could also reduce the hours that your staff spends on answering support tickets as well and just make it easier for your users to get things working on Pabbly Connect..
Looking forward to hearing back from you!

 

[Preeti Paryani]

Hello @apps,

We have escalated this issue to our technical team for further review. Please allow us some time and we will get back to you with an update as soon as we have any.

 

[Preeti Paryani]

Hello @apps,

Thank you for sharing the detailed feedback and the videos — we truly appreciate the time you took to document your observations.

After discussing this internally with our technical team, it appears that the misarrangement of router routes in the task history may occur based on how the routes were initially added. If the routes were created sequentially (i.e., adding a router, setting it up fully, saving it, and then creating the next one), they should appear in the correct order. However, if routes were cloned multiple times or saved non-sequentially, this can cause them to appear jumbled in the task history, as the backend registers them in the order they were saved.

Could you please confirm how the routes were set up — whether they were cloned, renamed later, or deleted and re-added at any point? This will help us analyze the behavior more accurately and guide you on the best approach.

 

[apps]

Hi;
Thanks for the answer and I'm happy you can use it.
I cannot remember exactly how it was setup as it has been done because I have developed and updated it over years so naturally things change, as in any development. I have probably cloned some of them and deleted some as well. I really can't remember. I understand that might be the technical reason but still, really it doesn't change the issue for me that the task history should reflect how it is currently. As a developer who build hundreds of flows that send data between each other and constantly makes changes naturally nothing is built in one go ever. All flows are an iterate process.

You can see it's a problem. It's impossible debug like this when the task history is so chaotic.

 

[Preeti Paryani]

Thank you for the detailed explanation. To help us review, could you please execute your workflow once without making any changes and share the most recent task history ID? This will allow us to analyze it on our end.

Regarding the routers appearing jumbled in the task history, this happens because the backend registers routes in the order they were saved sequentially. If routes were cloned or added non-sequentially, they may appear out of order. This behavior has been improved in the new UI, where cloned steps are added at the end rather than in between.

For now, the best approach is either to set up a workflow in the new UI or add a new router and manually add all routes in the correct sequence.

 

[apps]

Are you serious ("just" rebuild it)? This is a super unhelpful response because:
1. The new versions has so many issues and limitations that things won't work there. I already tried this and quickly learned even from your own team. Already wasted lots of time trying this.
2. Also this is a massive thing to ask me to setup. - setup the entire flow from scratch :-/ And what about all my other flows.

Can't you fix the bug in your software? I have clearly explained the issue, and everything that happens.

 

[ArshilAhmad]

Please allow us some time. We will get back to you with an update soon.