Please see this video:
As you can see the route names in the history does not match the actual names in the workflow which makes debugging extremely confusing. You think you're looking into the correct route but you're not because PC has the name wrong.
I have seen this across many flows for months but now I'm reporting it because it has become too big of an issue. Hope this can be resolved ASAP.
Example:
History: https://connect.pabbly.com/task/his..._id=IjU3NjEwNTY0MDYzZjA0MzI1MjZjNTUzZCI_3D_pc
Workflow:
Route named "Add Lines to existing Draft (should never match)" is named "Create Invoice with Lines" inside the history while the route named "Create Invoice with Lines" is named "Add Lines to existing Draft (should never match)" inside the history.
I hope it's clear how big of an issue this is.
I have seen this across many flows for months but now I'm reporting it because it has become too big of an issue. Hope this can be resolved ASAP.
Example:
History: https://connect.pabbly.com/task/his..._id=IjU3NjEwNTY0MDYzZjA0MzI1MjZjNTUzZCI_3D_pc
Workflow:
Pabbly - Online Marketing & Sales Software
Automate your sales and marketing with Pabbly. Unite email marketing, lead capture, WordPress themes, subscription all at one place.
connect.pabbly.com
Route named "Add Lines to existing Draft (should never match)" is named "Create Invoice with Lines" inside the history while the route named "Create Invoice with Lines" is named "Add Lines to existing Draft (should never match)" inside the history.
I hope it's clear how big of an issue this is.
Last edited: