BUG: Router names are incorrect in history - they are mixed around

Please see this video:
https://share.getcloudapp.com/DOukPDDo
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/history?filter_status=applied&filter_by_workflow_id=IjU3NjEwNTY0MDYzZjA0MzI1MjZjNTUzZCI_3D_pc
Workflow:
https://connect.pabbly.com/workflow/mapping/IjU3NjEwNTY0MDYzZjA0MzI1MjZjNTUzZCI_3D_pc

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.

Hey @apps

Kindly allow us some time we are currently looking into it. Further, can you record the video with voice since it does not begin very clearly?

Hi,

Thanks! I don't know why the video didn't get sound. But the video is not important actually. All it is showing is what I described above. P.S. I have corrected errors in my first post.
Problem is that the 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. Eg.route naming is incorrect and mixed around.
And this happens across many workflows and across nested routers as well. I hope it makes sense?

Hey @apps

We are currently looking into this, kindly allow us some time.