Hey there!
Most of the time, errors thrown by Mendix engine occur at runtime and are very unclear. Error message often don’t include the name of the microflow, and when it does, there’s no clear explanation why the microflow throws an error. This leads to waste of time, cause the only solution is to debug the app manually.
The suggestion : Mendix should include anonymous statistics in the Studio Pro in order to silently detect where most common errors are thrown, so they can improve both the error message, but also change whatever is required to avoid the developer to provoke such errors.