Overview
Use this checklist to quickly diagnose why a scheduled pipeline or scheduled workflow stopped running. Work through each check in order, the most common causes are listed first.
Checklist
scheduled-pipeline-checklist
| # | Check | Where to look | Details |
|---|---|---|---|
| 1 | Is the trigger actor still in the org? |
Project Settings → Triggers / Project Setup → Attribution
|
Read article → |
| 2 | Does the actor have context access? |
Org Settings → Contexts → Security groups
|
Read article → |
| 3 | Is "Prevent unregistered user spend" blocking the Scheduled Actor? |
Plan → Usage Controls
|
Read article → |
| 4 | Does the project have active followers? (workflows only) |
Projects → Follow/Unfollow
|
Read article → |
| 5 | Was there a recent config error on the target branch? (workflows only) |
Pipelines dashboard → target branch
|
Read article → |
| 6 | Does the target branch still exist? |
Your VCS repository
|
Recreate the branch or update the trigger. |
| 7 | Is SAML SSO in use? Has the session expired? |
GitHub org settings → SAML
|
Re-authenticate, then refresh permissions. |
Still not working?
If none of the above apply, check the CircleCI status page for active incidents. If the issue persists, contact CircleCI support with your project URL and the trigger name.
Comments
Article is closed for comments.