Storage usage not updated after deleting files for 24+ hours
storageHi Supabase team, I’m seeing a storage usage mismatch in my project and want to confirm whether billing/dashboard storage metrics are delayed or stuck.
Before cleanup, my project storage usage in the dashboard showed about 1.806 GB. I then deleted a large set of files from Supabase Storage.
After the cleanup, I verified directly from storage metadata that the current total remaining size in the files bucket is about 1,330,114,577 bytes, which is about 1.330 GB.
Breakdown:
The files were deleted more than 24 hours ago, but the Supabase dashboard/quota usage is still showing the older higher value and has not refreshed.
My questions:
Is Supabase storage usage/billing expected to lag by more than 24 hours after object deletion?
Is there any manual refresh or recalculation process for storage usage?
Could deleted objects still be counted in quota even though they are no longer present in storage.objects / bucket contents?
Is this a known dashboard reporting delay issue?
For context, the deletions were done through normal storage object deletion, not by deleting DB rows only.
Before cleanup, my project storage usage in the dashboard showed about 1.806 GB. I then deleted a large set of files from Supabase Storage.
After the cleanup, I verified directly from storage metadata that the current total remaining size in the files bucket is about 1,330,114,577 bytes, which is about 1.330 GB.
Breakdown:
The files were deleted more than 24 hours ago, but the Supabase dashboard/quota usage is still showing the older higher value and has not refreshed.
My questions:
Is Supabase storage usage/billing expected to lag by more than 24 hours after object deletion?
Is there any manual refresh or recalculation process for storage usage?
Could deleted objects still be counted in quota even though they are no longer present in storage.objects / bucket contents?
Is this a known dashboard reporting delay issue?
For context, the deletions were done through normal storage object deletion, not by deleting DB rows only.
