Debug your model
While developing your model it would be very useful to have a way of testing it in a controlled manner - for this you can start a debug session. Debug sessions run in the cloud and allows you to execute operations, view the output of these operations and view the console output (stdout and stderr) of your model.
For Node.JS models, you can also attach a remote inspector - this gives you additional features such as placing breakpoints and stepping through your code. This type of debugging can be very powerful. You can either use the debugger integrated into our browser-based editor, or you can connect any other remote debugger, such as Chrome devtools or Visual studio code.
Running a debug session
To start a debug session for a model, go to the model page, click "Edit code" (or "View code"), and locate the "Debug" button in the top right corner. You will then need to configure how to run your session. See launchers for more details.
If your model is using Node.js, you can choose to attach a remote inspector. As mentioned, this will allow you to place breakpoints and step through your code.
Once your debug session is running, you can view console output (stdout/stderr) by click the button "Debug output" at the bottom of your screen. To test your model, click "Call function", then select which function to call, and provide the required input parameters.
If you make any changes to your code, you will most likely need to restart the debug session for them to take effect.
Note: See pricing for details about billing for debug sessions.
