Show failed or skipped pipelines when VCS config fetch fails (e.g. Bitbucket 429)
R

Rachael Stanislaw
If CircleCI receives a webhook but cannot create a pipeline because Bitbucket (or another VCS) rate-limits the config fetch, nothing appears in the project pipelines list. There is no errored pipeline, no skipped because VCS rate limited row, and no customer-visible audit of the missed trigger.
Request: create a customer-visible failed/skipped trigger or pipeline entry with a clear reason (VCS rate limited, config fetch failed, etc.) so teams can detect and recover without manually noticing PRs with no CI.