CALL JAVASCRIPT ACTION with entity <> parameter — mxcli check passes, mxbuild fails with CE0115

[acarum]

When mxcli writes a nanoflow via exec containing a call to a JavaScript action whose parameter is typed entity <>, the resulting MPR is rejected by mxbuild with CE0115:

▎ "The arguments that are passed to JavaScript action 'NanoflowCommons.RefreshEntity' do not match the expected parameters and need to be refreshed."

mxcli check --references does not detect the problem — the check passes with no errors.

Steps to reproduce

1. JavaScript action with an entity <> parameter:
   NanoflowCommons.RefreshEntity(EntityToRefresh: entity <> not null)
2. MDL written by mxcli via exec:
   mdl
   create or modify nanoflow CustomModule.ACT_Example ()
   begin
   $Var = call javascript action NanoflowCommons.RefreshEntity(
   EntityToRefresh = ReferenceData.Dimension
   );
   return;
   end;
   /
3. ./mxcli check script.mdl -p "System.mpr" --references → ✅ Check passed
4. ./mxcli exec script.mdl -p "System.mpr" → ✅ Replaced nanoflow
5. ./mxcli docker check -p "System.mpr" → ❌ CE0115

Root cause (suspected)

Studio Pro internally stores a UUID binding for entity <> type parameters (generic entity type parameters). This binding is not written by mxcli exec into the MPR, leaving the call
structurally incomplete at the model level even though it is syntactically valid MDL.

Evidence: the identical nanoflow ReferenceData.ACT_CreateDimension, written by Studio Pro with the same MDL syntax, compiles without errors. DESCRIBE NANOFLOW emits the
same MDL for both, but the internal MPR representation differs.

Expected behavior

Either mxcli exec correctly serializes the entity UUID binding for entity <> parameters in JS action calls, or mxcli check detects the missing binding and blocks execution with an explicit
error rather than silently producing a broken MPR.

Environment

• Mendix: 11.12.4
• mxcli: 0.23.0

[github-actions]

Issue Triage

Summary:
The user reports that mxcli exec creates a nanoflow call to a JavaScript action with an entity <> parameter that passes mxcli check but fails during mxbuild with error CE0115, likely because the required UUID binding for the generic entity type is not written into the MPR.

Checklist of required bug‑report information

Required info	Present?	Details
mxcli version	✅	0.23.0
Mendix version	✅	11.12.4
Scenario (what the user was trying to do)	✅	Described MDL script, CLI commands (check, exec, docker check)
Expected output	✅	Either correct serialization of the entity UUID binding or mxcli check detecting the missing block
Experienced output	✅	mxcli check passes, mxbuild fails with CE0115
AI bug report (mxcli diag --bundle or session log)	❌	Not provided

What’s missing:
The issue would benefit from the output of mxcli diag --bundle (or at least the relevant session log) to help diagnose the internal state when the nanoflow is written.

Polite request:
Could you please attach the output of mxcli diag --bundle (or the relevant session log) to the issue? This will give us more insight into what’s happening during the exec step and help us resolve the problem faster. Thank you!

---

Automated triage via OpenRouter — workflow source