Repository navigation
check passes a called workflow whose parameter is not $WorkflowContext (build: CE1613); syntax help shows that form #1530
Description
Summary
check passes a called workflow whose parameter is not named $WorkflowContext (native build: CE1613), and mxcli syntax workflow call-workflow shows that form.
Repro
workflow M.WF_Child
parameter $Task: M.Item
begin
end workflow;
workflow M.WF_Parent
parameter $WorkflowContext: M.Item
begin
call workflow M.WF_Child(Task = $WorkflowContext);
end workflow;
mxcli check --references: 0 errors.mxcli exec: succeeds.mx check: CE1613.
Renaming the child parameter to $WorkflowContext and the mapping to (WorkflowContext = ...) builds clean.
Expected
checkrejects a workflow parameter that is not namedWorkflowContext, because a Mendix workflow has exactly one context parameter with that name.- The example in
mxcli syntax workflow call-workflow,CALL WORKFLOW HR.SubApproval(Request = $WorkflowContext) AS callWf1;, is changed to the form that builds. (The example is still printed by v0.27.0.)
Tested with: a five-app lab project (Mendix 11.15, mxcli v0.26.0), reproduced in a probe. The help example was re-read on v0.27.0; the build behaviour was not retested there.
Activity
github-actions commentedon Oct 16, 2026
Issue Triage
Summary:
The
mxcli checkcommand incorrectly allows a called workflow whose parameter is not named$WorkflowContext, while the Mendix build fails with error CE1613.Checklist for bug report completeness
mxcli check --referencescommandcheckshould reject a workflow parameter not named$WorkflowContextcheckreports 0 errors,execsucceeds, butmx checkyields CE1613Missing information:
Please provide the output of
mxcli diag --bundle(or at least the relevant session log) so we can investigate the issue further. Thank you!Automated triage via OpenRouter — workflow source