Repository navigation
Workflow call microflow: a target with a System.Workflow parameter fails build with CE0117 although check demands the mapping #1523
Description
Summary
Workflow call microflow: a target with a System.Workflow parameter fails the build with CE0117 although check demands the mapping. Related: closed #948 (workflow feedback). No existing issue found.
Repro
- Microflow
M.MF_Step (Workflow: System.Workflow). - A workflow with
call microflow M.MF_Step (Workflow = $Workflow) caption '...'(every spelling tried). mxcli checkdemands the mapping;mxbuildreports CE0117 Unknown variable 'Workflow'.- Separately: an activity named
closefails to parse (keyword); see also the parse-message issue for workflow MDL.
Expected
check and mxbuild agree. close is listed as reserved in mxcli syntax workflow.
Actual
check and build disagree. The only way through was dropping the parameter and reaching the instance via System.Workflow_ParentWorkflow.
Tested with: Mendix 11.15.0, mxcli v0.26.0 on macOS (code also read in the v0.27.0 source). Not retested on v0.27.0.
Activity
github-actions commentedon Oct 16, 2026
Issue Triage
Summary:
The user reports that
mxcli checkinsists on mapping aSystem.Workflowparameter in a workflow → microflow call, butmxbuildfails with error CE0117 (“Unknown variable 'Workflow'”), causing a mismatch between check and build.Checklist of required bug‑report information
checkandmxbuildshould agree;closelisted as reservedclosemxcli diag --bundleor session log)Missing information:
Please provide the output of
mxcli diag --bundle(or at least the relevant session log) so we can inspect the internal state and reproduce the problem more reliably.Thank you for reporting the issue! Once the diagnostic bundle is added, we’ll be able to investigate further.
Automated triage via OpenRouter — workflow source
Merge pull request #1419 from ako/fix/1529-workflow-expression-scope