AI & Agent Dev Bug Sandbox Back to Radar

Persistent 504 Errors On Supabase Auth Endpoints Due To Database Connection Pool Exhaustion During Peak Hours

Project zvusdpixljxkxlxrrauj (Pro) experiences 5xx/504 errors on /auth/v1/* during weekday business hours, primarily affecting token refresh and user lookup endpoints. The issue is likely caused by database connection pool exhaustion in the GoTrue auth service under concurrent load, leading to requests exceeding the 60-second timeout.

highConfidence 70%Supabase

Origin Analysis

The GoTrue auth service is configured with an insufficient database connection pool size. During peak business hours, concurrent token refresh and user lookup operations exhaust the pool, causing requests to queue and exceed the 60-second timeout, resulting in 504 Gateway Timeout errors.

1. During peak hours (06:00-15:00 UTC weekdays), send concurrent requests to /auth/v1/token?grant_type=refresh_token and /auth/v1/user endpoints.\n2. Observe that a subset of requests hang and return 504 after 60 seconds.\n3. Check database pool metrics and note that the pool is saturated.

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

Increasing the pool size may put additional load on the PostgreSQL database, potentially degrading overall performance if the database lacks sufficient resources. Monitor database CPU, memory, and connection counts after applying the change. Consider using PgBouncer for more efficient connection pooling. To rollback, revert to the previous configuration values.