AI & Agent Dev Bug Sandbox Back to Radar

Management API Upgrade POST Returns 201 But Creates No Observable Upgrade Status

The Supabase Management API accepts a Postgres upgrade request with HTTP 201 and returns a tracking_id, but no upgrade status record is created. Status endpoints return databaseUpgradeStatus: null indefinitely, and the database remains on the old version. Users cannot determine if the orchestration job is queued, failed, or safe to retry.

highConfidence 73%Node.js

Origin Analysis

The upgrade endpoint enqueues an asynchronous orchestration task and returns 201 before atomically persisting a tracking record. If the tracking record insertion or queue publication fails after the response is committed, the returned tracking_id has no backing state, causing status APIs to return null.

1. Hosted project on older Postgres 17 patch. 2. GET /v1/projects/{ref}/upgrade/eligibility returns eligible true without blockers. 3. POST /v1/projects/{ref}/upgrade with target_version and release_channel from eligibility. 4. Receive HTTP 201 with non-empty tracking_id. 5. Poll GET /v1/projects/{ref}/upgrade/status?tracking_id=... and GET /v1/projects/{ref}/upgrade/status. 6. Observe databaseUpgradeStatus: null and database version unchanged after estimated duration.

Fixing Code Block

0x7F 45 4C 46 02 01 01 000x90 12 AB 04 C1 7E 33 08
0xA4 1C 90 3E 77 0B D2 580x11 F6 6A 2C 80 19 DE 44
0x00 00 00 00 03 00 3E 000x01 00 B7 4D 55 90 0C 61
0x6C 69 62 63 2E 73 6F 2E0x36 00 8E 17 42 AA 05 F3
0xDE C0 DE 01 8B 45 FC 890xC7 5D 20 6F 91 03 E4 78
0x13 37 00 4F 9A 2D E1 700x08 B4 5C 22 71 D0 4A 16
0x48 8D 3D 22 01 00 00 E80x91 FF 0A 63 2E 57 B8 04
0x5A 91 C3 0E 44 70 1B 880x02 6F 39 C4 15 80 ED 27
0xFF 15 40 20 60 00 48 890xC3 90 7A 01 4C 28 B1 56
0x0F 1F 44 00 00 55 48 890xE5 C3 18 6D 92 0B 33 A7

Edge Case Audit

Requires a database migration to create the database_upgrade_status table or ensure columns. Historical orphaned tracking IDs from before the fix remain unresolved and will still return null. Deploying while an upgrade is in progress could create duplicate active records if no unique partial index exists; add one on project_ref where status in ('queued','running'). Do not roll back mid-upgrade; verify status before downgrade.