Retry Bitbucket Cloud config fetches on HTTP 429 (honour Retry-After)
R

Rachael Stanislaw
When CircleCI receives a Bitbucket webhook and then gets HTTP 429 fetching .circleci/config.yml, the trigger ends with no pipeline. There is no delayed retry that honours Bitbucket Retry-After / rate-limit headers and recreates the pipeline.
Impact: bursty automation (orb releases opening PRs across many repos in the same minute, engineer PR batches, Renovate rebases) permanently loses CI for that event. Teams only discover it when a PR has no CircleCI status. Bitbucket user OAuth identities are limited to about 1,000 API calls/hour; workspace access tokens scale higher, but classic Bitbucket OAuth projects still fetch config with a user OAuth connection.
Request: on vcs-provider-rate-limited / Bitbucket 429 during webhook-driven config fetch, delay and retry per Retry-After (with bounded retries) so a temporary throttle does not permanently drop the pipeline.