Repository navigation
check passes an out-of-scope variable in a workflow call microflow argument (build: CE0117) #1529
Description
Summary
check passes an out-of-scope variable in a workflow call microflow argument; the native build reports CE0117.
Repro
M.ACT_Bind takes Workflow: System.Workflow.
workflow M.WF_Probe
parameter $WorkflowContext: M.Item
begin
call microflow M.ACT_Bind(Workflow = $Workflow, Item = $WorkflowContext);
end workflow;
mxcli check --references: 0 errors.mxcli exec: succeeds.mx check: CE0117, the expression is invalid.
With Workflow = $WorkflowInstance all three pass.
Expected
check validates workflow argument expressions against the variables in scope ($WorkflowContext and $WorkflowInstance only) and reports something like "unknown variable $Workflow; in a workflow use $WorkflowInstance".
Why it matters
The error shows up only at the native build, after exec has written the model. Agents tend to guess $Workflow because microflows name the parameter that way.
Tested with: a five-app lab project (Mendix 11.15, mxcli v0.26.0), reproduced in a probe. Not retested on v0.27.0.
Activity
github-actions commentedon Oct 16, 2026
Issue Triage
Summary:
The
mxcli checkcommand fails to detect an out‑of‑scope variable ($Workflow) used in a workflow’scall microflowargument, allowing the model to passcheckandexecbut later causing a native‑build error (CE0117).Checklist for bug report completeness
mxcli v0.26.0mxcli check --references,mxcli exec,mx check)checkshould report unknown variable$Workflowand suggest$WorkflowInstancemx checkreturns CE0117;mxcli check --referencesshows 0 errors;mxcli execsucceedsMissing information:
Could you please provide the output of
mxcli diag --bundle(or at least the relevant session log) so we can inspect the internal state when the issue occurs? This will help us reproduce and fix the problem.Thank you for reporting this! Once we have the diagnostic log, we’ll be able to investigate further.
Automated triage via OpenRouter — workflow source
Merge pull request #1419 from ako/fix/1529-workflow-expression-scope