In OutSystems Platform, a Request results from a browser request to the Platform Server, an awakened Timer action, a Process instance execution, or a called Web Service method exposed by an eSpace. The execution of the request follows what is designed for it in the eSpace as, for example, an action to be executed when a button is pressed (browser request) or a Web Service method (Web Service method call).

To debug a request you have to suspend its execution at the point where you want to examine eSpace elements and runtime values. See how to Suspend the Execution.

Debug Environment

Once a request execution is suspended for debugging, that request is added to the Requests Tab on the Debugger Tab with its current execution stack of eSpace elements. The rest of the Debugger Tab is filled in with the requests's debug information on eSpace elements and runtime values.

In the Requests Tab, double-clicking on any eSpace element displays it on the canvas.

Debugging Requests

To debug a request use the Debugger commands available in the Debugger Toolbar or in the Debug Menu. The request being debugged, i.e., the active request, is identified by a blue arrow in the Requests Tab, as well as the eSpace element being debugged on canvas.

You may have multiple requests suspended for debugging at the same time. In this case, you may only debug one at a time (the active one) and all the other requests are kept suspended (inactive) and marked with greys arrows, as well as their eSpace element on the canvas (if visible). To change from active request simply double-click on the request you want to debug in the Requests Tab, and Service Studio automatically updates the Debugger Tab with the debug information for that request.

If the eSpace element being debugged does not belong to your eSpace (e.g. an eSpace reference, an action in a Producer eSpace, etc.) it cannot be visualized on the canvas, and will only be displayed in the Requests Tab with its name followed by its eSpace name between brackets.

Any modifications you make to your eSpace while debugging won't take effect until you publish or run your eSpace again. Meanwhile, the modified eSpace elements will have visual feedback in the Requests Tab with the following overlay icons:

Missing Element: the element is no longer present in your eSpace but still exists in the published version of the eSpace; the missing element will still be debugged though it will not have visual feedback on the canvas;

Modified Element: the element is different from the one that is published; the element that is going to be debugged is the published one and not your modified one.

Aborting a Request Execution

While debugging a request you may abort its execution, thus terminating it. For that, use the button Abort Request available on the Debugger Toolbar or in the Debug Menu.

See Also

Debug an eSpace | Debugger Tab | Debugger Toolbar | About Breakpoints | Debug Menu