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.
The user is experiencing an HTTP 544 DatabaseTimeout error when attempting to download a private object from a managed Supabase project in the us-west-2 region. The error occurs through both the authenticated REST endpoint and S3 endpoints, despite other database operations succeeding. The user seeks a workaround for exporting Storage objects under these conditions.