Debug Automation Controller#
The user can trigger the debugging process of any workflow from the workflow designer, using breakpoints on points of entrance of tasks. Pressing the Debug button on the top ribbon will present three options to the user:
- Mock Debug
- Remote Debug
- Profiler Debug
After pressing the button, the debugger panel will open. Upon pressing the Start button, the debugger will start listening for breakpoint events and subscribe to the necessary message bus subjects according to the current debug mode. Separate panels for variables and breakpoints are available to the user.
Info
If the current debug mode is the Mock debug, starts the engine. If not, starts the ping event to request the controller instances availability state.
Mock Debug#
Starts a debug session without actually connecting to an instance, focusing on the workflow execution itself. A Restart button is available so that the workflow can be put in the starting state once again.
Remote Debug#
Allows connecting to a remote instance and inspect the context being executed. A Machine Connection panel is available to select the instance to which the debugger should connect.
Profiler Debug#
This mode will attach a profiler that will record all the variables, call stack and sequence and memory usage of the workflow throughout its execution. This profiler session can then be downloaded and examined offline or reloaded afterwards to the debugging panel. As in the Remote Debug option, a Machine Connection panel is available to select the instance to which the debugger should connect. Also, a Load Session button is available for the user to load a previously saved session, as described above.


