Repository navigation
Two unhelpful parse messages in workflow MDL (reserved activity name close, exposed before returns) #1533
Description
Summary
Two unhelpful parse messages in workflow MDL.
- An activity named
close(for examplecall microflow M.ACT_Close as close) gives a bare parse error becausecloseis a keyword. Measured on v0.27.0: "mismatched input 'close' expecting {IDENTIFIER, QUOTED_IDENTIFIER}". The message should say the name is reserved. - A microflow with
exposed as workflow actionwritten beforereturns Boolean as $Xfails with "mismatched input 'returns' expecting STRING_LITERAL" on v0.27.0 (reported as "expecting BEGIN" on v0.26.0). The order must bereturnsfirst. A hint such as "returns must come before exposed" would save a round trip. Without the hint the error reads as if exposed microflows cannot return a value, which is wrong: Boolean and enumeration returns both work in the right order.
Tested with: mxcli v0.27.0 (mxcli check, both messages re-measured), Mendix 11.15.
Activity
github-actions commentedon Oct 16, 2026
Issue Triage
Summary:
The user reports two unclear parse errors in workflow MDL when using
mxcli check: a reserved‑word activity name (close) and an ordering issue withexposedbeforereturns.Checklist of required bug‑report information
mxcli checkon workflow MDL with an activity namedcloseand a microflow havingexposed as workflow actionbeforereturns Boolean as $Xcloseand a hint thatreturnsmust come beforeexposedMissing information:
Please provide the session log or the output of
mxcli diag --bundle(or at least the relevant log excerpt) so we can examine the parsing context and reproduce the issue.Thank you for reporting this—adding the diagnostic log will help us improve the error messages quickly!
Automated triage via OpenRouter — workflow source
learn(workflow, fixture-seeding): a jump has one fixed target; probed…
Merge pull request #1430 from ako/fix/1533-parse-hints-keyword-name-a…