See difference between crash and long-running action when debugging environment - Mendix Forum

See difference between crash and long-running action when debugging environment

2

Hola people,

As far as I know, there is no way (when my debugger is connected to an app running in the Mendix cloud or other remote server) to see the difference between a long running action and the situation where an error occurred: while staying in the desktop modeler that is. I could go back to the screen to see if an error pop-up has appeared or my 'running now' tab in sprintr, but seeing a crash occur in the modeler in this situation would be the preferred solution.

I know it would help me in my debugging activities! Stretch-objective: see the resulting log from the crash on the Mendix environment in my desktop modeler log :)

asked
0 answers