When developing and testing in Qodly Studio, the throw command is handy for stopping code execution and alerting an error message. The command behaves differently depending on whether a debug session has been started or not. When the debugger is inactive, throw will issue the error message on the front end (as long as the “Provide feedback” setting is toggled ON for the event).



In contrast, when the debugger is active, the error message will be displayed in the debugger instead, in the function where the throw line exists.