Overview
You set your scheduled pipeline's Attribution to Scheduled Actor (Scheduling System) but the pipeline never fires. This usually happens when your organization has the "Prevent unregistered user spend" setting enabled.
Why this happens
The Scheduled Actor is not a registered CircleCI user, it is a system-level identity. When Prevent unregistered user spend is turned on, CircleCI blocks all pipelines triggered by unregistered users, which includes the Scheduled Actor.
How to check
Click Plan in the sidebar.
Select the Usage Controls tab.
Check if Prevent unregistered user spend is toggled on.
How to fix
Go to Project Settings and find your schedule trigger:
GitHub OAuth / Bitbucket Cloud: Select Triggers in the sidebar.
GitHub App: Select Project Setup in the sidebar, then locate your pipeline's schedule.
Click Edit on the scheduled trigger.
Change the Attribution from Scheduled Actor (Scheduling System) to an actual registered CircleCI user.
Save the trigger.
The scheduled pipeline will start running under that user's identity on the next scheduled time.
Note: If the schedule uses contexts with security group restrictions, make sure the user you choose has access to those contexts.