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
Update the retry logic to look for the Retry-After header, and respect the suggested wait time if one is provided.
We should also setting a max wait time, so that the request will fail rather than waiting an inordinate amount of time. A decent max setting might be between 30 seconds to 10 minutes - somewhere in that range. If we wait too long, it becomes increasingly likely that the user may have moved on from the page/operation/etc. that triggered the request (especially considering that we don't yet support cancellation; see #208)
For longer wait periods caused by rate limiting, returning an error explaining the delay would be preferable to the request hanging for an hour or longer. That way we can explain the delay to the user directly.
The text was updated successfully, but these errors were encountered:
Update the retry logic to look for the
Retry-After
header, and respect the suggested wait time if one is provided.We should also setting a max wait time, so that the request will fail rather than waiting an inordinate amount of time. A decent max setting might be between 30 seconds to 10 minutes - somewhere in that range. If we wait too long, it becomes increasingly likely that the user may have moved on from the page/operation/etc. that triggered the request (especially considering that we don't yet support cancellation; see #208)
For longer wait periods caused by rate limiting, returning an error explaining the delay would be preferable to the request hanging for an hour or longer. That way we can explain the delay to the user directly.
The text was updated successfully, but these errors were encountered: