GitHub Actions "schedule disabled after 60 days of inactivity"

Scheduled (cron) workflows are automatically disabled after 60 days without any repository activity. The cron stops firing silently until a commit re-activates it or you re-enable the workflow. This is policy, not a runner fault.

What this error means

A previously working scheduled workflow no longer runs, and the workflow shows as disabled in the Actions tab.

This scheduled workflow was disabled automatically because the repository
had no activity for 60 days. Re-enable it to resume scheduled runs.

Common causes

60 days without repository activity

No pushes or other activity occurred, so GitHub auto-disabled the schedule to save resources.

Workflow left disabled

The workflow remains disabled until explicitly re-enabled or activity resumes.

How to fix it

Re-enable the scheduled workflow

1. Open the workflow in the Actions tab and choose Enable workflow.
2. Push a small commit to register activity if needed.
3. Confirm the cron resumes on the next scheduled tick.

gh workflow enable nightly.yml

How to prevent it

• Keep the repository active, or re-enable scheduled workflows after long quiet periods.
• Monitor critical cron workflows so a silent disable is noticed quickly.

Related guides