-
Notifications
You must be signed in to change notification settings - Fork 662
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
document how to change retry configuration #305
Comments
Hello! It should execute your CB when it retries the endpoint. If it is not, that is a bug for sure! At the moment, there is no way to disable retrying—is the existing logic not working for you? It might be a nice feature if we added a web api retry policy so you could specify how throttling should be handled. What do you think? |
Hi! Thank you for the quick reply, I hope you are enjoying the holidays! I think the existing retry logic works great for most projects, but mine would benefit from being able to turn it off. The problem with not being able to cancel the retry is that X seconds after the API call failed that message probably contains stale data and I would rather cancel that API call and make new one with fresh data. |
you can now completely customize the retry behavior by passing a configuration object as changing this issue into a docs issue to make this more clear. |
For the slack bot I'm working on I need to keep references to the bot's messages timestamps.
I've been using the callback of web.chat.postMessage to do that, however, I noticed that if the request errors because of rate limits it says it will retry in 1 second.
Does that retry execute the callback again?
Is there a way to disable retrying so I can manage throttling manually?
Thanks!
The text was updated successfully, but these errors were encountered: