Adding Retry Parameter
See original GitHub issueI have one API that time to time returns ECONNRESET
. So I’d like to do retry on such an error. Do you have plans to add retry
feature to this library?
Issue Analytics
- State:
- Created 8 years ago
- Comments:23 (4 by maintainers)
Top Results From Across the Web
Configuring Retry parameters for HTTP HTTP(s) Transport
Procedure ; Retry Count, Set the value to use as a number of retries for HTTP connection. ; Retry Interval, Set the value...
Read more >Set Retry Parameters - Syniti
Set Retry Parameters · Select Interfaces in the Navigation pane. · Click the Events icon for the desired interface. · Click Vertical View...
Read more >Guide to Spring Retry - Baeldung
A quick and practical guide to implementing retry logic with Spring Retry.
Read more >How to Implement Retry Logic in C# - Code Maze
In this article, we are going to learn how to implement retry logic in C# to help us handle problems that we can...
Read more >Retry decorator in Python - Medium
api/status , takes the parameter “id” returned from api/getData , and checks ... To make any function as a retry logic , just...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@mericsson I am too in need of exponential backoff when retrying. I’ve put together the following which works great. You my want to add in checking for specific errors/status codes as this currently just intercepts and retries all errors.
To use:
Config Options:
retry
- Number of times to retry the request after first failed request.retryDelay
- Number of milliseconds to wait in between failed requests (defaults to 1).I may make this a bit more configurable in a gist at some point.
Something like this! It retries 500 errors once.