msteams: maxRetryWait param to control waiting after 429 responses - #235
Merged
Merged
Conversation
ibodrov
previously approved these changes
Apr 30, 2026
eau-defemme
approved these changes
Aug 24, 2026
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.
MS Graph API may return relatively huge durations to wait after a 429 response (e.g.
600seconds) which may be far longer than reasonable for a process to sleep before a retry. If the response-givenRetry-Afteris higher than themaxRetryWaitparam, then the task call ends with an exception (or silently ends ifignoreErrorsistrue).maxRetryWaitto control when to give up retrying instead of waiting for a rate limit reset30000ms (30s)