Fix 'PessimisticConcurrencyConflict' next to 'Conflict' error codes #799
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.
In PR 787 we added a retry for 409 conflict errors.
We now get almost the same error so I added an "or" statement.
We get the following error:
{"error":{"code":"PessimisticConcurrencyConflict","message":"Operation on the API is in progress","details":null}}This pull request updates the HTTP retry logic to handle an additional error scenario related to concurrency conflicts. The main focus is on improving the robustness of retry decisions when a 409 response status is encountered.
Improvements to error handling and retry logic:
HasConflictErrorhas been renamed toHasConflictOrPessimisticConcurrencyConflictError, and its logic expanded to check for bothConflictandPessimisticConcurrencyConflicterror codes in the response.