Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
As a Stream user, I should be able to correctly respond to Facebook rate limit exceptions. Currently, any error from the Facebook Graph API results in a call to the exponential backoff strategy. This is fine if we are actually getting requests throttled/rate limited, but can result in very slow Stream completion if the error is related to something else (like a bad Page ID).
We need to ensure that we only use the backoff strategy when we are being rate limited.
Acceptance Criteria:
- Determine which error codes represent potential rate limiting/throttling exceptions
- Only call the backoff when our requests are being throttled.