Repository navigation
describe workflow drops the call workflow parameter mapping #1531
Description
Summary
describe workflow drops the parameter mapping of a call workflow activity, so describe followed by exec does not round-trip.
Repro
Exec a parent workflow containing call workflow M.WF_Child(WorkflowContext = $WorkflowContext/M.Parent_Current/M.Item);. Native mx check is clean. Then run mxcli describe workflow M.WF_Parent.
Actual
The output shows call workflow M.WF_Child; with no mapping.
Expected
describe emits the mapping. Without it, a describe-edit-exec loop silently removes the mapping, and the build then fails or passes the wrong object.
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
describe workflowcommand omits the parameter mapping of acall workflowactivity, causing a describe‑edit‑exec loop to lose the mapping.Checklist for bug report
call workflowactivity, then ranmxcli describe workflow M.WF_Parentdescribeshould emit the mapping (e.g.,call workflow M.WF_Child(WorkflowContext = $WorkflowContext/M.Parent_Current/M.Item);)call workflow M.WF_Child;with no mappingMissing information:
Could you please provide the output of
mxcli diag --bundle(or at least the session log) so we can investigate the issue further? Thank you!Automated triage via OpenRouter — workflow source
Merge pull request #1418 from ako/fix/1531-call-workflow-parameter-ma…