Files
supabase/apps/docs
KrisDevX 66ed5b3a95 docs: correct the built-in retry behaviour in the supabase-js retry guide
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.
2026-10-01 13:15:55 +03:00
..
2026-07-01 12:59:00 +02:00

Reference Docs

Supabase Reference Docs

Maintainers

If you are a maintainer of any tools in the Supabase ecosystem, you can use this site to provide documentation for the tools & libraries that you maintain.

DocSpec

We use documentation specifications which can be used to generate human-readable docs.

  • OpenAPI: for documenting API endpoints.
  • SDKSpec (custom to Supabase): for SDKs and client libraries.
  • ConfigSpec (custom to Supabase): for configuration options.
  • CLISpec (custom to Supabase): for CLI commands and usage.

The benefit of using custom specifications is that we can generate many other types from a strict schema (eg, HTML and manpages). It also means that we can switch to any documentation system we want. On this site we use Next.js, but on Supabase's official website, we use a custom React site and expose only a subset of the available API for each tool.

Contributing

To contribute to docs, see the style guide for how to write a page, and the developers' guide and contributing guide for repo mechanics. If you write with an AI coding agent, use the /write-the-docs skill to draft and /edit-the-docs to revise an existing page.