Issue

Runtime errors occur where the nanoflow stack trace indicates issues with specific microflow calls. However, the stack trace displays the ID of the microflow instead of its name, making it difficult to identify the problematic microflow, especially when the nanoflow contains numerous microflow calls.

The stack traces will resemble the following:

Nanoflow stack:
"Call microflow: oY5QV/Z4nF28w6Y/FG0iZQ" in nanoflow "Core.NF_Example"

Environment

Studio Pro (all versions)

Cause

The issue arises because the nanoflow stack trace originates from the client side, where displaying the microflow name is restricted due to security features. Furthermore, it is not possible to search for microflows by ID in Mendix Studio Pro, as the ID is generated on export and is not available during development.

Solution/Workaround

The easiest way to identify the problematic microflow in these cases would be to set the IDResolution log node to Trace. This log node provides information on retrieval queries and runtime operations that are being executed and contains both the name and the ID of the microflow. The following documentation explains how to achieve this:

• Configuring Log Levels Within Studio Pro - When running an app locally in Studio Pro.
• Log Levels - When running an app in a Mendix Cloud node.

Once the IDResolution log node is enabled, check the logs for entries that contain both the microflow ID and its corresponding name. This information will help identify the problematic microflow in the stack trace.

Additional information 

Mendix documentation:

• Log Nodes
• Configuring Log Levels Within Studio Pro
• Log Levels