feat: exponential backoff on consecutive 429s from Parcel API - #86
Merged
Merged
Conversation
Doubles the retry interval on each consecutive 429 (300s -> 600s -> 1200s ...), floored at the user's configured interval and capped at 1h. Resets to zero on the first successful response. Prevents the integration from continuing to poll at the same cadence when the Parcel API is enforcing a rolling/burst rate limit beyond the documented 20/hr.
Owner
Author
|
Hey @PineappleEmperor ! If you have a moment to check this PR out, if not, no worries. Hope you're doing well! :) |
Collaborator
|
Hallo! I'm alive! Hope all is well with you! |
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
2 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.
Doubles the retry interval on each consecutive 429 (300s -> 600s -> 1200s ...), floored at the user's configured interval and capped at 1h. Resets to zero on the first successful response. Prevents the integration from continuing to poll at the same cadence when the Parcel API is enforcing a rolling/burst rate limit beyond the documented 20/hr.