The Robot Editor contains a specialized mode for debugging robots. You can switch between design and debug mode by clicking on one of the two mode buttons placed in the left corner of the Robot Editor. You can also switch to the debug mode by clicking the icon in the toolbar in Design Studio Main Window. Alternatively, if you want to debug from the current step in Design Studio, you can click the icon. When you switch to the debug mode the Robot Editor will change appearance, and look as shown below.
The top of the Robot Editor in debug mode also contains a Robot View, similar to that of the design mode. Note, however, that the Robot View in debug mode has a current step only when you are actually debugging the robot. This current step is not always the same as the current step in the Robot View in the design mode.
Below the Robot View is a large panel divided into four sub-panels, the main panel and three panels named "Summary", "Stop When" and "Steps to Skip".
In the main panel, you see the results of the debugging process divided into four tabs. In the "Input/Output" tab, you see a list of all used variables, if any, and a list of all values that have been returned so far during the debugging process. In the "API Exceptions" tab, you see a list of the API exceptions reported so far during the debugging process. In the "Log" tab, you can see whatever has been written to the log so far during the debugging process. (Some actions, particularly those that take a while to execute, such as the Loop Form action, write status information to this log. Step errors will also be logged if the step is so configured.) Whenever the debugging process has been temporarily stopped, the "State" tab shows the robot state that is input to the current step. The "State" tab contains seven sub-tabs. The "Variables" sub-tab shows the list of variables. The "Windows", "Cookies", and "Authentications" sub-tabs show the state, in much the same way as the State View in Design Studio with its associated dialogs. The "Local Storage" and "Session Storage" sub-tabs shows the HTML5 objects that have been persisted locally. The "API Exception" sub-tab contains the API Exception generated at the current step, if any. For all API Exceptions (and the errors that form part of them), you can click the Goto button to go directly to the step that generated the error — that is, the step that generated the error will become the current step in Design Studio.
In the "Summary" panel, you see an overview of the number of variables returned or written to a database and generated API exceptions so far during the debugging process.
In the "Stop When" panel, you can specify the criteria for when the debugging process should temporarily stop (besides ending normally).
For more on debugging robots, see How to Debug a Robot.