You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When interacting through flow you have to now handle rate limits as the new limits are way more agressive then what they used to be. Having to modify client code to add that is quite the effort.
(Optional): Suggest A Solution
When interacting with the flow chain through flowkit it would be nice to be able to automatically retry requests that fail due to rate-limiting using set policies.
Would it be an option when creating a flowkit.State to add some policies for retrying, and have those only retry on 429.
This library for instance is really flexible around retry and it is not specific to http/grpc.
Issue To Be Solved
When interacting through flow you have to now handle rate limits as the new limits are way more agressive then what they used to be. Having to modify client code to add that is quite the effort.
(Optional): Suggest A Solution
When interacting with the flow chain through flowkit it would be nice to be able to automatically retry requests that fail due to rate-limiting using set policies.
Would it be an option when creating a flowkit.State to add some policies for retrying, and have those only retry on 429.
This library for instance is really flexible around retry and it is not specific to http/grpc.
https://github.com/avast/retry-go
(Optional): Context
The text was updated successfully, but these errors were encountered: