Troubleshooting Schedules Failing to Trigger

Sometimes, issues can occur where a defined scheduled pipeline or workflow can fail to trigger when it is defined to do so.

This can appear in the form of nothing appearing, or the pipeline being generated in the "CREATED" state without running anything.

In OAuth organisations, this is commonly due to a permissions issue.

How OAuth Organisations Trigger Schedules

Due to the nature of how OAuth permissions work, whenever a schedule triggers, it must make use of a valid actor within CircleCI in order to trigger the pipeline.

This means that even if the default CircleCI scheduler is used, a valid, active user is required on that project for the trigger to work.

If you are seeing this issue, please ensure that the relevant project has at least one valid, active follower.

If the project has no followers, you should ensure that someone begins following the project, or if there are already followers, perform a re-authentication to ensure that the permissions are not stale.