2) Retry 500s#66
Merged
Merged
Conversation
sam-watttime
approved these changes
Apr 15, 2026
nsteins
approved these changes
Apr 20, 2026
sam-watttime
force-pushed
the
retry-500s
branch
from
d7a9a3a to
d6afe46
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
3 participants
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.
What
Make the request session more robust to intermittent issues.
Why
So that users of the client, e.g. a "hungry analyst", can more easily retrieve data despite intermittent 500 issues
How
Introduce a Retry class to the sessions that checks for 500, 502, 503, and 504 and retries 3 times.