`create or modify association` reports "Modified association" but keeps the old owner when the association crosses modules

[MendixMau]

Environment

• mxcli: built from main @ 95091765 (v0.24.0-165-g95091765), 2026-09-27. First seen on v0.23.0.
• Mendix / mxbuild: 11.12.2, blank app from mx create-project (MPR v2)
• OS: macOS (Darwin 25.6, arm64)

Reproduction

Same setup as #1223 (modules ModA and ModB, entities ModA.GuestGroup, ModB.App, ModA.Tag, ModA.Guest).

create association "ModA"."GuestGroup_App"
from "ModA"."GuestGroup" to "ModB"."App"
type Reference
owner Default;

create or modify association "ModA"."GuestGroup_App"
from "ModA"."GuestGroup" to "ModB"."App"
type Reference
owner Both;

$ mxcli exec 02b-modify-owner-xmod.mdl -p Repro.mpr
Reconciled 1 access rule(s) for new association
Created association: ModA.GuestGroup_App
Modified association: ModA.GuestGroup_App
$ mxcli -p Repro.mpr -c 'DESCRIBE ASSOCIATION "ModA"."GuestGroup_App"'
...
owner Default

Variant (fresh copy each time)	exec says	describe shows afterwards
ModA.Tag → ModA.Guest (same module), Default → Both	Modified association	owner Both
ModA.GuestGroup → ModB.App (cross-module), Default → Both	Modified association	owner Default

Expected

owner Both, as in the same-module case, or an error saying the owner of a cross-module association cannot be changed this way.

Actual

Success message, owner unchanged.

The only workaround is drop + create. That gives the association a new ID, so existing links in the database are lost, and with owner Both it then runs into #1223.

[github-actions]

Issue Triage

Summary:
The create or modify association command reports success but fails to change the owner of a cross‑module association, leaving it as Default instead of Both.

Checklist of required bug‑report information

Required info	Present?	Details
mxcli version	✅	v0.24.0-165-g95091765 (built from main)
Mendix version	✅	11.12.2 (MPR v2)
Scenario (what was tried)	✅	mxcli exec with an MDL script to change association owner from Default → Both
Expected output	✅	Owner should become Both (or an error if cross‑module changes aren’t allowed)
Experienced output	✅	Success message printed, but DESCRIBE ASSOCIATION still shows owner Default
AI bug report (session log or mxcli diag --bundle)	❌	Not included

What’s missing:
To help diagnose the issue, could you please provide the session log from the failing run (or run mxcli diag --bundle and attach the resulting archive)? This will give us the internal state and any additional error details.

Thank you for reporting the problem! Once we have the log, we’ll be able to investigate further.

---

Automated triage via OpenRouter — workflow source