Hi,
For now when an exception occurs, it is a little complicated to determine the origin of the problem, especially when it occurs before using the app (so after launching run locally). The logs are mostly unreadable/ not user friendly.
It would be interesting to have the possibility to directly point the origin of the error in the associated microflow or nanoflow, and the associated variables operations.