mirror of
https://github.com/supabase/supabase.git
synced 2026-10-07 02:15:05 +03:00
KrisDevX
66ed5b3a95
The "Built-in retries for PostgREST queries" section described behaviour
that supabase-js does not have.
It said POST requests are retried. RETRYABLE_METHODS is GET, HEAD and
OPTIONS, and shouldRetry returns false for anything outside that list, so
a write is never replayed. This was the most consequential of the errors,
because it invites a reader to skip their own handling for failed writes.
It listed 408, 409, 503 and 504 as the retried statuses. The actual list
is RETRYABLE_STATUS_CODES, which holds 520 and 503.
It described the backoff as exponential with jitter. getRetryDelay is
Math.min(1000 * 2 ** attemptIndex, 30000), which has no random component.
Also noted that .rpc() sends POST unless called with { get: true }, so
RPC calls are not covered by the built-in retries despite the intro
listing .rpc() alongside .from().
Corrections only. The page structure and the fetch-retry section are
unchanged.