Basic Debugging

To switch to debug mode, click the icon or the Debug button in Design Studio. To start debugging the robot, click the icon.

The Debug Mode of the Robot Editor

As the robot is being executed in debug mode, you can watch the current location in the Robot View. You can also watch the results of the execution in the main panel. In the "Input/Output" tab, the "Input" panel shows the input variables, if any, and the "Output" panel shows all values that have been returned so far during the execution. If the robot has no input variables, the "Input" panel is not shown. In the "API Exceptions" tab, you can see all API exceptions that have been generated so far during the execution. In the "Log" tab, you can see what has been written to the log so far during execution. In the "State" tab, you can see the robot state, if any. Also, in the "Summary" panel to the right of the main panel, you can see a summary of the execution, containing the number of returned values, the number of API exceptions generated, statistics on the number of HTTP requests, the amount of sent and received data, and the number of JavaScript instructions that have been executed.

It is important to understand that execution in debug mode is independent of the execution done in design mode in Design Studio. Therefore, debug mode has its own current step and its own current robot state, independent of the current step and current robot state in design mode. In debug mode, the current step is the step that is about to be executed, or is being executed, in the debugging process, and the current robot state is the input to that step.

You can stop the debugging at any time by clicking the icon. You can also make the debugging stop when certain events occur. This is done in the "Stop When" panel. Here, you can choose whether the debugging should stop when values are returned, when API exceptions are reported, and when breakpoints are reached. Of course, debugging will always stop when the execution of the robot has completed.

When debugging has stopped, you can see the reason for the stop in the status bar at the bottom of the Robot Editor. If the debugging has stopped before the execution of the robot is complete, you can watch the current robot state in the "State" tab. The "Variables", "Windows", "Cookies", and "Authentications" sub-tabs show the robot state in the same way as in the State View in Design Studio. The "API Exception" sub-tab shows the API exception, if the execution stopped because an API exception was reported.

If debugging has stopped before the execution of the robot is complete, you can resume the debugging by clicking the icon. You can also restart the debugging by clicking the icon. This will abort the current debugging process and make the debugger ready to start a new debug from the start of the robot. The debugging is also restarted automatically whenever the current robot is modified or replaced by another robot in Design Studio.

If the robot has input variables, the input values of these can be edited in the "Input" panel, and when you press Enter, the debugging will be restarted with the new input values. The input values cannot be edited while a debug is running, so if you want to change the input values, you must first restart the debugging.