My Docs uses MY_DOCS ordinal (3), not enum id (4)

Shipped: July 7, 2026 at 2:01 AM UTC
Author: kamo
Commit: d18ad86

The backend resolves ImageAssocType via `values()[assocType]` (ordinal index) and persists it @Enumerated(ORDINAL). Every imaging surface passes the ordinal, but the My Docs doc-manager passed the enum's explicit id (4). Ordinal 4 is MEET_RECORDING, so My Docs documents were stamped assoc_id=4 and resolved to the non-existent imaging-meet-recordings bucket instead of imaging-mydocs — making them un-downloadable, un-convertible, and un-editable (edit showed "Document not converted"). Their bytes were always in imaging-mydocs. Use ordinal 3 (MY_DOCS).

All changes

Like what you see shipping?

Every one of these updates lands in your workspace automatically. Start free and watch it grow week after week.

Start Free Forever View Pricing