Repository navigation
fix: spread capture retry waits by up to 25% - #1058
Merged
Merged
Conversation
eli-r-ph
marked this pull request as ready for review
October 13, 2026 18:04
eli-r-ph
force-pushed
the
v1-retry-jitter
branch
from
October 14, 2026 03:11
656d125 to
25ecc88
Compare
eli-r-ph
force-pushed
the
v1-identity-context
branch
from
October 14, 2026 03:11
7ed86bf to
4dbd65a
Compare
eli-r-ph
force-pushed
the
v1-retry-jitter
branch
from
October 14, 2026 03:48
25ecc88 to
ca906e4
Compare
eli-r-ph
force-pushed
the
v1-identity-context
branch
from
October 14, 2026 03:48
4dbd65a to
3e65c58
Compare
This was referenced Oct 20, 2026
dustinbyrne
approved these changes
Oct 20, 2026
dustinbyrne
left a comment
dustinbyrne
left a comment
Contributor
There was a problem hiding this comment.
The retry jitter is applied before the 30-second cap and preserves the bounded Retry-After floor across both capture lanes. No issues found in this PR’s delta.
AI-assisted review.
eli-r-ph
force-pushed
the
v1-identity-context
branch
from
October 20, 2026 17:16
3e65c58 to
727e867
Compare
eli-r-ph
force-pushed
the
v1-retry-jitter
branch
3 times, most recently
from
October 20, 2026 23:40
61dc3f7 to
dcdaae1
Compare
eli-r-ph
force-pushed
the
v1-identity-context
branch
from
October 20, 2026 23:40
683f1b5 to
d8d308c
Compare
eli-r-ph
force-pushed
the
v1-retry-jitter
branch
from
October 21, 2026 00:25
dcdaae1 to
de17b11
Compare
eli-r-ph
force-pushed
the
v1-identity-context
branch
from
October 21, 2026 00:25
d8d308c to
a1ddf21
Compare
eli-r-ph
force-pushed
the
v1-retry-jitter
branch
from
October 21, 2026 00:44
de17b11 to
dcdaae1
Compare
eli-r-ph
force-pushed
the
v1-identity-context
branch
2 times, most recently
from
October 21, 2026 01:03
d8d308c to
a1ddf21
Compare
eli-r-ph
force-pushed
the
v1-retry-jitter
branch
from
October 21, 2026 01:03
dcdaae1 to
de17b11
Compare
eli-r-ph
force-pushed
the
v1-identity-context
branch
from
October 22, 2026 17:27
a1ddf21 to
36f39d2
Compare
Clients that fail together now retry at slightly different times, so they do not all hit capture at once while it recovers. Retry-After still sets a minimum wait, and the 30 s cap still applies. Co-Authored-By: Claude Opus 5.5 <[email protected]>
eli-r-ph
force-pushed
the
v1-retry-jitter
branch
from
October 22, 2026 17:32
de17b11 to
fd2a202
Compare
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
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.
💡 Motivation and Context
Stacked on #1053. Capture retries used fixed waits, so clients that failed together all retried at the same moment and could overload capture again as it recovered. This PR spreads each wait.
Changes
Retry-Afterheader is still a minimum; the spread never shortens it.💚 How did you test it?
Retry-Afteras a floor.🤖 Agent context
Autonomy: Human-driven (agent-assisted)
Written with Claude Code under the direction of the assignee.
🤖 Generated with Claude Code