Repository navigation
Grammar: no boundary events on CALL WORKFLOW #1532
Description
Summary
Grammar: no boundary events on call workflow. Mendix supports interrupting and non-interrupting timer boundary events on a Call workflow activity. mxcli accepts a boundary clause on call microflow and on wait for notification, but on call workflow the same clause is a parse error.
Repro (mxcli check alone)
create workflow Tmp.WF_Parent
parameter $WorkflowContext: Tmp.Item
begin
call workflow Tmp.WF_Child(WorkflowContext = $WorkflowContext) as callChild
boundary event interrupting timer addDays([%CurrentDateTime%], 1) { end workflow; };
end workflow;
Actual (v0.27.0): "mismatched input 'boundary' expecting ';'" and "mismatched input 'interrupting' expecting SUBPROCESS". The same clause after a call microflow parses.
Expected
The same boundary syntax is accepted on call workflow, so a parent can put a deadline on a child without moving the timer into the child.
Tested with: mxcli v0.27.0 (parse), Mendix 11.15.
Activity
github-actions commentedon Oct 16, 2026
Issue Triage
Summary:
The user reports that mxcli fails to parse a boundary timer event on a
call workflowactivity, while the same syntax works forcall microflow.Checklist of required bug‑report information
call workflow … boundary event …Missing information:
Please provide the output of
mxcli diag --bundle(or at least the relevant session log) so we can examine the parsing context and any additional diagnostics.Once that’s added, the report will be complete. Thank you for bringing this to our attention!
Automated triage via OpenRouter — workflow source