GitHub Actions "workflow disabled due to repository inactivity"
GitHub disables scheduled and some automated workflows in repositories that have gone inactive, so they stop running until re-enabled. This commonly affects forks and dormant repos. It is a platform policy, not an infrastructure failure.
What this error means
A workflow does not trigger and is marked disabled, typically in a fork or a repository with no recent activity.
github-actions
Workflow "scheduled-sync.yml" is disabled because the repository has been inactive.
Enable it from the Actions tab to resume runs.Common causes
Repository inactivity
The repo has had no activity, so automated/scheduled workflows were disabled.
Fork with Actions disabled
Forks often have workflows disabled until the owner explicitly enables Actions.
How to fix it
Enable Actions and the workflow
- In the Actions tab, enable Actions for the repository if prompted.
- Enable the specific disabled workflow.
- Push activity to keep it active going forward.
GitHub CLI
gh workflow enable scheduled-sync.ymlHow to prevent it
- Re-enable Actions and key workflows on forks and dormant repositories.
- Maintain periodic activity for repos that depend on scheduled automation.
Related guides
GitHub Actions "schedule disabled after 60 days of inactivity"Fix a GitHub Actions scheduled workflow that stopped firing because it was auto-disabled after 60 days of rep…
GitHub Actions "workflow_run did not trigger" (default branch only)Fix a GitHub Actions workflow_run that never fires because the triggered workflow file only exists/runs on th…
GitHub Actions "pull_request paths filter excluded all (no run)"Fix a GitHub Actions workflow that never runs because its pull_request paths or paths-ignore filter excluded…