CREATE MICROFLOW accepts calls to non-existent microflows without error

[retran]

Impact

Creates broken cross-references in the model. Errors only surface when Studio Pro opens the project — no feedback at authoring time.

Steps to Reproduce

CREATE MICROFLOW MyModule."Test" ()
RETURNS Boolean AS $Result
BEGIN
  DECLARE $Result Boolean = true;
  CALL MICROFLOW MyModule."DoesNotExist"();
  RETURN $Result;
END;

Actual Result

Command succeeds. No error or warning. Model contains a dangling reference.

Expected Result

Error (or at minimum a warning) when the call target does not exist in the project.

Severity

Low

---

Discovered during AI-assisted manual testing session (2026-04-29, mxcli v0.7.0-257-ga07e7e0).

[github-actions]

Issue Triage

Summary:
The issue reports that mxcli allows a CREATE MICROFLOW statement to call a non‑existent microflow without emitting an error, leaving a dangling reference in the model.

Checklist (bug report):

• ✅ mxcli version (provided: v0.7.0-257-ga07e7e0)
• ❌ Mendix version of the project
• ✅ Scenario (MDL script creating a microflow that calls another)
• ✅ Expected output (error or warning when target missing)
• ✅ Experienced output (command succeeds, no warning, dangling reference)
• ❌ AI bug report (output of mxcli diag --bundle or session log)

Missing information:
Please add the Mendix version of the project you’re working with and, if possible, attach the output of mxcli diag --bundle (or at least the relevant session log) so we can reproduce the environment and investigate further. Thank you!

---

Automated triage via OpenRouter — workflow source