When developing a custom activity in Visual Studio you could previously attach the debugger to the UiPath Executor and use that to run through your code, hitting breakpoints etc.
It seems after an update of Studio I can no longer do this, I have 3 instances of the executor I could attach to and I believe the one I need to won’t let me since there is already a debugger attached.
Can anyone else confirm this behaviour before I register a bug with UiPath?
I also commented on this old topic related which also includes the ‘classic’ debugging steps but it didnt get any notice.