You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On a managed Supabase project in us-west-2, downloading one existing private object returns HTTP 544 DatabaseTimeout through the authenticated REST endpoint and both S3 endpoints. The request was made without concurrent downloads. A separate PostgreSQL query and the database export succeeded.
Is there a supported workaround for exporting Storage objects when both REST and S3 return 544? I can provide the project ref and request ID privately.
This discussion was converted from issue #53469 on November 16, 2026 20:02.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
On a managed Supabase project in us-west-2, downloading one existing private object returns HTTP 544 DatabaseTimeout through the authenticated REST endpoint and both S3 endpoints. The request was made without concurrent downloads. A separate PostgreSQL query and the database export succeeded.
Is there a supported workaround for exporting Storage objects when both REST and S3 return 544? I can provide the project ref and request ID privately.
All reactions