Was this helpful?
Debugging a Process
You can debug a process based on the breakpoints set for the steps. Breakpoints allow you to pause the execution of a process so that you can check the state at a given point and verify the design behavior. It provides insights into design problems and failures.
Note:  Break points are enabled when processes are run from the Studio IDE only. Steps can only be debugged within the Studio. If debug mode is enabled for a step and the process is saved, the debug state will not be saved. This behavior ensures that processes aren’t run from the engine with step debugging enabled. This would result in paused execution that can only be resolved by user intervention.
When you enable the debug option for a step, the process execution pauses prior to step execution and displays the values of the associated variables and properties of DJMessages. After viewing these values and properties, you can continue process execution from the paused step or stop the process execution.
Note:  You cannot debug the Start step.
To enable or disable debug option for step(s):
1. On Step Builder Canvas, right-click the step that you want to debug during process execution and select Enable Debug.
A small icon is displayed at the corner of the step to indicate that the debug option is enabled for the step.
Note:  You cannot enable debug option for a disabled step.
To disable the debug option for a step, right-click on the step and select Disable Debug. The small debug icon is removed from the corner of the step.
To enable the debug option for multiple steps, press Ctrl and select the steps. Right-click and select Enable/Disable Debug on Step(s). The debug option is enabled for the selected steps.
2. Click /download/attachments/24976276/Map_Run.png?version=1&modificationDate=1490826089046&api=v2 to run the process.
The process execution is paused at the step for which debug was enabled and the Paused at <stepname > window displays the associated global variables with values. Currently, only Variant, DJMessage (includes unbound messages), Macros, and single dimension Array variables are supported.
3. In the left pane, click the variable to view the associated values.
4. (optional) Specify a file name with path (for example D:\debug.txt) in the Save all to file text box or browse and select an existing file, and then click Save.
Note:  If you select an existing file, log messages are appended to this file.
5. Click Continue to proceed with process execution or click Stop to end the process execution.
Last modified date: 02/09/2024