Errors / checked October 9, 2026
This scheduled workflow is disabled because there hasn't been activity in this repository for at least 60 days.
The error
The Actions tab of a public GitHub repository with an on: schedule workflow and no recent commits.
Quick fix
- Open the Actions tab, select the workflow and click Enable workflow. The schedule starts again.
- It will be disabled again after another 60 days without repository activity, so pick one of the longer-term options below if the job matters.
Why this happens
GitHub turns off scheduled workflows in public repositories after 60 days with no activity. Scheduled workflows are also disabled by default in forks.
Other solutions
- Trigger the workflow with workflow_dispatch or repository_dispatch from an outside scheduler instead of on: schedule.
- If the job only needs to call a URL, skip Actions and have a hosted scheduler call that URL. RunLater does this on any cron schedule and keeps a log of each response.
Check a schedule before you deploy it: the cron expression explainer shows the next 10 run times.
Have the URL called on schedule, with retries
RunLater calls your URL on a cron schedule or at an exact time, in your timezone, retries failed calls with backoff and logs each response, so a timeout or a 5xx shows up in a log instead of disappearing.
Start a 14-day trialStarter is $15/month for 250 scheduled requests and 25,000 runs. Cancel before day 14 and you pay nothing.