If the hourly rate limit is not hit, but the API abuse mechanism is triggered, the API won't handle this gracefully. Instead, it bails. I think the ideal case here would be to wait for a small random amount of time (< 5 seconds perhaps, with some backoff) and retry