Mendix has a pretty ok debugging toolset, but what is missing is the option “Break on error”.
Because this is no option at this moment, you need to run it a couple of times, set breakpoints just before the activity that causes the error. Usually this in not that hard nore time consuming, but when it is happening in a loop, it becomes more cumbersome. You need to find out at what values the error occurs.
This idea suggests to add the option “Break on error”.
Yes, this would be a nice addition. Also the differentiation between caught and uncaught exceptions
I completely support this. It will be hugely useful. Every other programing language has this feature.
java – https://help.eclipse.org/2019-12/index.jsp?topic=%2Forg.eclipse.jdt.doc.user%2Freference%2Fviews%2Fbreakpoints%2Fref-addexception_viewaction.htm
javascript – https://umaar.com/dev-tips/32-pause-on-exception/
Even outsystems has this – https://success.outsystems.com/Documentation/11/Developing_an_Application/Troubleshooting_Applications/Debugging_Applications/Breakpoints