Add ability to go to causing action from an error log lne - Mendix Forum

Add ability to go to causing action from an error log lne

10

When an error is printed in the console log it is very hard to track down the cause.

The microflow name is usually somewhere in the log (albeit not the easiest to see) but for the causing action only the type is shown. Even in a moderately sized microflow there will be several retrieve or change object actions making it hard to figure out which one caused the error.

It would be great if I can right-click the error and have an option to go to the action that caused it.

Current look:

 

Suggested improvement:

asked
0 answers