The continuation orb is not the only CircleCI API consumer. We have some jobs that monitor workflows, workarounds for mutex and other jobs that also perform API requests.
We noticed that on peak times the API calls may fail with error 429 (Too many request).
CircleCI support suggested to read the HEADER
We implemented the retry with backoff on our scripts but we rather that the official continuation orb would take care of that edge case on the official orb.
Describe Requests
The continuation orb is not the only CircleCI API consumer. We have some jobs that monitor workflows, workarounds for mutex and other jobs that also perform API requests.
We noticed that on peak times the API calls may fail with error 429 (Too many request). CircleCI support suggested to read the HEADER
We implemented the retry with backoff on our scripts but we rather that the official continuation orb would take care of that edge case on the official orb.
Thanks!