When debugging a new flow in Studio, I wish the activities are numbered and when an error occurs, describe the error like it does now, but indicate the activity number as well. This would make it easier to locate the activity to correct.
Are you suggesting this in addition to it being highlighted in red? Surely thats enough to know what activity is the issue?
yes its a good suggestion
I think activity numbering could also be helpful when sharing errors with other developers. Instead of explaining which activity failed or sharing screenshots, we could simply refer to the activity number from the error message. It could make troubleshooting and team collaboration easier.
You guys dont seem aware, the current errors from UiPath DO tell you what activity has failed so you can get straight to it an activity.
Unless you have really bad naming with a sequence with a ton of ‘assign’, ‘assign’ ‘assign’ or loads of IF statements all named the same you can find the activity no problem.
Here is an example on my exception mail where I format the workflow trace thats included in an exception (caveat being it has to be on an invoked workflow, the trace doesnt appear if its from the main).
This scenario includes the stack trace into a library activity also. There are alot of generic ‘Sequences’ in there, but thats cause they are hidden by default in alot of activities now so you can’t change the names. Regardless I can use this to immediately find the error activity even though I was quite lazy in renaming my activities.
There is also already an activity ID in an error, but as far as I know this number is related to the generated code. I havent looked into how to match that to a specific activity yet based on this ID. It doesnt appear in the xaml from what I can tell.
