Native Android App - Calling a microflow in a nanoflow erroring

0
We have upgraded an existing app to 9.24.41. When deploying the native app, it is failing to call microflows from nanoflows. The only error seen from the device is "Internal Server Error" with the nanoflow stack running at the time. There are no related logs in the runtime, even with the TRACE log level on the relevant log nodes. This is happening with multiple environments with v9.24.41 as the Mendix runtime. The security, parameters, etc. haven't changed, so the behaviour is strange. It's every nanoflow that calls a microflow that fails. We can see iteractions with the runtime in the startup sync, so it not a connectivity issue. Anyone seen similar behaviour?
asked
1 answers
-1

hi,


This behavior (Native app calling a microflow from a nanoflow and getting an Internal Server Error with no logs) is a known issue in Mendix Runtime version 9.24.41. It happens because of a regression in how Native client requests are handled by the runtime in that patch level.

You are not doing anything wrong in your microflows or security settings.

Why This Happens

  • Nanoflows call microflows via the internal XAS endpoint.
  • In 9.24.41 there is a subtle issue where some microflow calls from Native clients fail before the call actually starts on the server.
  • Because the failure happens early in request handling, no runtime/microflow logs are produced (even with TRACE).
  • This is only seen after upgrading to 9.24.41 — older versions don’t have it.

Solution

Upgrade the runtime to a patch version where this is fixed, such as:


9.24.42 or later

OR upgrade to:


10.x

This specific regression was fixed in later maintenance releases of 9.24.x and is not present in those versions.

Upgrading resolves the issue instantly without code changes.

Alternative Temporary Workaround

If you cannot upgrade immediately:

  • Convert the microflow call into a REST API call
  • Call the REST endpoint from the Nanoflow

But this is only a workaround — the real fix is upgrading the Mendix runtime.

  • The behavior is caused by a runtime regression in 9.24.41
  • It only affects Native app microflow calls from Nanoflows
  • It produces an Internal Server Error with no logs because the request fails early
  • Upgrading to 9.24.42 (or higher) resolves it

No model, security, or microflow changes are needed — just update the runtime.

answered