Retry transient Durable Object routing failures#399
Merged
Conversation
PartyServer now retries transient Durable Object infrastructure errors at the routing boundary so callers do not need to wrap every routeAgentRequest or routePartykitRequest use site themselves. The retry path is scoped to retryable, non-overloaded runtime errors and recreates the DO stub/request per attempt while avoiding rerunning user routing hooks. This also exposes routingRetry configuration, documents the option, and covers retry, opt-out, overload, non-retryable, exhausted, body replay, and onRetry observer edge cases. Co-authored-by: Cursor <cursoragent@cursor.com>
🦋 Changeset detectedLatest commit: 03e3aad The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
hono-party
partyfn
partyserver
partysocket
partysub
partysync
partytracks
partywhen
y-partyserver
commit: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
routingRetrysupport to PartyServer routing so transient Durable Object infrastructure errors are retried at theroutePartykitRequest/getServerByNameboundary.retryable === true, never retries overloaded errors, recreates the DO stub per attempt, and clones routed requests so request bodies remain replayable.Details
This keeps retry handling in PartyServer instead of requiring downstream frameworks or apps to wrap every
routePartykitRequest/routeAgentRequestcall site. User routing hooks (onBeforeConnect/onBeforeRequest) still run once before the retry boundary, so retries do not repeat auth or request-mutation hooks.routingRetrydefaults to 3 attempts with jittered exponential backoff (100msbase,800mscap). It can be disabled withroutingRetry: falseor configured withmaxAttempts,baseDelayMs,maxDelayMs, andonRetry.Test plan
npx vitest -r src/tests src/tests/index.test.ts --watch falsenpm run check:typenpm run check:formatnpm run check:lintMade with Cursor