Retry when encountering secondary rate limit
Closed this issue · 1 comments
charlietsai commented
From the docs, both RETRY_COUNT
and RETRY_SLEEP
have a default value but I noticed that there is no retry attempt when we encounter this error:
Error: Caught error trying to compare base with head: You have exceeded a secondary rate limit. Please wait a few minutes before you try again.
I am guessing this is intentional since retrying too frequently will only contribute to the request rate and exacerbate the issue.
However, I am looking into circumventing the rate limit by setting a high-enough RETRY_SLEEP
. In my case, the alternative is waiting and manually triggering the auto-update job again so I don't mind if RETRY_SLEEP
is a very high value. I just don't want to have to manually intervene.
Is there a way to retry when encountering the rate limit?
charlietsai commented
I have a temporary workaround for now from using an infrequently running scheduled job