Address: timeout while waiting for state to become 'success' #807
Conversation
This file contains 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
Addtionally, set retries timeouts across the provider to minimum 2min.
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.
Add 1 minute timeout limit to api calls lifecycle.
Additionally, set retries timeouts across the provider to minimum 2min.
Second attempt and hopefully definitive to...
Close #780
The first attempt brought by #802 didn't make it, because the granularity timeout configuration introduced with that update was not actually covering the whole lifecycle of api request hanging, due to multiple reasons in client/server side depending on the scenario the provider was running in. However, this simpler and more straightforward configuration proved to be the solution to make the provider able of gracefully retrying the calls once the new timeout was reached.