Issue

When troubleshooting, it is possible to encounter error messages or log messages with obfuscated runtime operation IDs. With the runtime operation IDs scrambled, it is difficult to know what runtime operation is causing the issue. Example messages are as follows:

In the error message:

Executing runtime operation failed for security reasons: <INSERT_RANDOM_CHARACTERS>

In the app logs:

"Executing runtime operation failed for security reasons: <INSERT_RANDOM_CHARACTERS>" "WARNING - WebUI: User '<INSERT_USER>' attempted to execute runtime operation '<INSERT_RANDOM_CHARACTERS>' but does not have the required permissions"

Cause

These runtime IDs are obfuscated. However, the operations.json file can be used to find the runtime operation that is referenced in the error message.

Environment

Applications hosted in all deployment types

Solution/Workaround

Inside the deployment/model directory is the operations.json file which contains the mapping between the obfuscated operation IDs and the actual operation.

When running locally, this file is accessible as mentioned above.

If running on the Mendix Cloud, please download the deployed MDA file from the cloud, and then unzip the MDA using 7zip to extract the files. The operations.json file will still be in the model folder.

The operations in the file will look like the following as an example: 

{"operationId": <INSERT_RANDOM_CHARACTERS>","operationType":"callMicroflow","parameters":{"ReturnURL":["String"]},"constants":{"MicroflowName":"<INSERT_MICROFLOW_NAME>"},"allowedUserRoleSets":[["<USER_ROLE>"]]},

Use the operation ID from the error message to find the relevant operation that is failing due to security reasons. Then, investigate further why this operation would fail.

Operation IDs scramble again after a redeployment, so ensure these IDs are checked against files related to the same deployment.