AI & Agent Dev Bug Sandbox Back to Radar

Storage Stuck In 'Coming Up…' After Restart Due To Database Schema Reset, Project Never Reaches ACTIVE_HEALTHY

A Supabase Free-plan project in ap-northeast-2 is stuck in COMING_UP state for over a month because the Storage service cannot start. Symptoms indicate the PostgreSQL database was unintentionally reset: storage.buckets and storage.objects are empty, public schema has 0 tables, schema_migrations is missing, and auth.users has only one row. This leaves no self-service recovery as pause/restore is disabled in COMING_UP state.

criticalConfidence 75%Supabase

Origin Analysis

The project's database appears to have been reset or corrupted during a routine restart, likely due to an infrastructure fault or migration failure on the Free-tier backend. The Storage service requires its catalog tables (storage.buckets, storage.objects) and associated schemas to initialize. With those missing, Storage health checks fail with ABORTED REQ and object requests return HTTP 544, which prevents the project from reaching ACTIVE_HEALTHY. The platform's state machine disables pause/restore in COMING_UP, trapping the project without self-service recovery.

1. Have a Free-plan Supabase project running normally in ap-northeast-2. 2. Restart the project via dashboard. 3. Observe all services return Healthy except Storage, which remains 'Coming up…'. 4. Project status stays COMING_UP indefinitely (1+ month). 5. Attempt recovery: Pause button disabled; restore_project API rejected because state is COMING_UP, not PAUSED. 6. Verify Storage failures: health endpoint returns ABORTED REQ; public objects return HTTP 544; SQL queries show storage.buckets and storage.objects empty; public schema has 0 tables; schema_migrations missing; auth.users has only 1 row.

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

This script assumes the existence of a force-pause API flag and a restore endpoint; both may not be available or may require special permissions. Running restore will overwrite the current database state with the selected backup, causing irreversible data loss for any data created after that backup. Do not execute without confirming a valid backup exists and without explicit authorization. Rollback: before restore, take a manual dump of the current database (even if partial) using pg_dump or Supabase dashboard export. If restore fails, project may remain in an inconsistent state requiring manual intervention.