Skip to content

Make transient errors retryable - #6400

Draft
tantaman wants to merge 1 commit into
mainfrom
repro
Draft

Make transient errors retryable#6400
tantaman wants to merge 1 commit into
mainfrom
repro

Conversation

@tantaman

@tantaman tantaman commented Aug 21, 2026

Copy link
Copy Markdown
Contributor

Codex authored. Currently reviewing.


  • Client retries HTTP 408/425/429/5xx and timeout errors. HTTP 4xx, parse/configuration
    errors, and explicit retryable: false remain terminal. packages/zero-client/src/client/
    error.ts:138

  • Ambiguous client/server Internal and database errors get three reconnects before entering
    error. A stable connection or explicit connection.connect() resets the budget. packages/
    zero-client/src/client/zero.ts:2152

  • Added an optional wire-level retryable marker. Older 1.8 clients safely ignore it; they
    require an upgrade to gain the new client behavior. packages/zero-protocol/src/
    error.ts:25

  • zero-cache API calls now have a 10-second timeout per attempt, covering headers and
    response-body reads. Timeouts, network failures, and retryable HTTP statuses receive four
    backend attempts. Exhaustion is reported with retryable: true. packages/zero-cache/src/
    custom/fetch.ts:87

@vercel

vercel Bot commented Aug 21, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
replicache-docs Ready Ready Preview Aug 21, 2026 4:10pm
zbugs Ready Ready Preview Aug 21, 2026 4:10pm

Request Review

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant