No delay after final retry on max attempts #129
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.
This MR addresses an issue where a delay is still applied after the final attempt, even when the maximum number of attempts for a specific error type has been reached.
Problem:
When using the
retry.AttemptsForError()
option to define a custom attempt limit for a specific error type, the retry logic still applies the configured delay after the final permitted attempt for that error. This results in unnecessary wait time and inconsistent behavior.Steps to Reproduce:
Observed Output:
Expected Output: