We founded an issue with the catch trace and logs while running the process in debug mode.
The issue is the next: If you have an error in the Try box, but in the catch the first activity has an error, the log, the tracking, and the call stack shows nothing until the flow leaves the try catch activity.
The process work as expected knowing that, but until we noticed the problem (an add data row activity without the right variable reference, it happened using the testactivity feature) it drove us nuts.
Relevant info, can not show more, due security restrictions by the client.
Studio 2020.10.6 - 3/2/2021
License Provider: Orchestrator
Microsoft Windows Server 2016 Datacenter 64-bit
.NET Framework Version 4.8 or later