Overview
Your scheduled workflow (defined in config.yml with triggers: - schedule:) was running daily and stopped without any changes to your configuration. This is usually caused by a follower/token issue or by a config error on a non-scheduled build.
No valid project followers
Scheduled workflows require at least one active project follower with a valid OAuth token. If all followers have left the organization, unfollowed the project, or their tokens have expired, the schedule stops silently. This happens after third unsuccessful attempt to trigger the workflow.
How to check:
There is no UI to see a list of project followers. Go to the Projects page and check if the Follow button appears next to your project. If it does, no one on your team may be following it.
How to fix:
Go to Projects in the sidebar.
Find the project and click Follow.
If the Follow button gives an error, check your VCS repository settings for duplicate CircleCI webhooks and remove any extras.
The schedule should resume on the next scheduled time after a valid follower is added.
A config error unscheduled the workflow
If a non-scheduled build on the same branch (usually main or master) triggers a Config Processing Error, CircleCI unschedules all scheduled workflows on that branch. The schedules will not resume until a successful build with a valid config runs on that branch.
How to check:
Look at the most recent non-scheduled pipeline on the target branch. If it shows a build error or config processing error, that is the cause.
How to fix:
Fix any issues in your
.circleci/config.yml.Push a commit to the target branch.
Confirm the build succeeds.
The scheduled workflow will be automatically re-registered after a successful build.
Scheduled workflows vs. scheduled pipelines
This article covers scheduled workflows (defined in config.yml using triggers: - schedule:). If you are using scheduled pipelines (defined in the UI under Project Settings → Triggers), see Scheduled pipelines instead. Scheduled pipelines have different triggering mechanics and are not affected by project followers.