Retry transient API errors with exponential backoff#129
Merged
Conversation
Transient network conditions can result in timeouts that can often be retried successfully.
carlosantoniodasilva
added a commit
to judoscale/judoscale-node
that referenced
this pull request
Mar 5, 2026
Retry up to 3 times for transient errors, matching the behavior of Python and Ruby. judoscale/judoscale-python#129 judoscale/judoscale-ruby#265
carlosantoniodasilva
added a commit
to judoscale/judoscale-node
that referenced
this pull request
Mar 5, 2026
Retry up to 3 times for transient errors, matching the behavior of Python and Ruby. judoscale/judoscale-python#129 judoscale/judoscale-ruby#265
This was referenced Mar 5, 2026
carlosantoniodasilva
added a commit
to judoscale/judoscale-node
that referenced
this pull request
Mar 5, 2026
Retry up to 3 times for transient errors, matching the behavior of Python and Ruby. judoscale/judoscale-python#129 judoscale/judoscale-ruby#265
carlosantoniodasilva
added a commit
to judoscale/judoscale-java
that referenced
this pull request
Mar 5, 2026
…sts (#12) Similar logic for retry backoff from the Ruby/Python/Node packages. Also update the timeout seconds to 5 to match across the board. judoscale/judoscale-node#97 judoscale/judoscale-python#129 judoscale/judoscale-ruby#265
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.
Transient network conditions can result in timeouts that can often be retried successfully.
Note
Medium Risk
Adds retry/backoff behavior around metrics posting; low complexity but changes runtime network behavior and could affect reporting latency under failure conditions.
Overview
Reporter now retries transient network failures when posting metrics.
Reporter._report_metricsretries up toMAX_RETRIES(3) onConnectionError/Timeoutwith exponential backoff, and logs a dedicated warning if it still cannot connect.Non-transient
requestserrors (e.g., HTTP failures) still log once and abort without retry. Tests were added to assert retry vs non-retry behavior while patchingrequests.post/time.sleep.Written by Cursor Bugbot for commit ab3f002. This will update automatically on new commits. Configure here.