GitHub Actions / GitHub Actions

GitHub Actions Scheduled Cron Workflows Not Triggering on Self-Hosted Runners

Fix GitHub Actions cron-scheduled workflows that don't run on self-hosted runners Includes evidence for GitHub Actions troubleshooting demand.

Source-backed Last updated May 13, 2026 2 sources Needs local verification

Category: GitHub Actions
Error signature: GitHub Actions scheduled cron task does not trigger on self-hosted runner
Quick fix: Compare the failing environment with a known working setup, then change one configuration value at a time.
Updated: May 13, 2026
Verification status: Source-backed
Evidence: 2 public source URLs

Before you change production

This page includes public source URLs in the imported troubleshooting record. Compare those references with your version and environment before applying changes.

Reproduce the smallest failing action and save non-secret logs before changing configuration.
Check versions for GitHub Actions, related SDKs, package managers, CI runners, and hosting providers.
Change one setting or dependency at a time, then rerun the same failing command or request.
Avoid destructive commands, credential rotation, billing changes, or security relaxations without a rollback plan.

What this error means

GitHub Actions scheduled cron task does not trigger on self-hosted runner is a GitHub Actions failure pattern reported for developers trying to fix github actions cron-scheduled workflows that don't run on self-hosted runners. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

GitHub Actions runner issue #4210 confirms scheduled cron tasks don't trigger on self-hosted runners. Multiple people report the same problem on community discussions forum (#185024). Affects automated CI/CD pipelines relying on self-hosted infrastructure.

Common causes

Self-hosted GitHub Actions runners don't trigger scheduled cron workflows even though the workflow YAML is correctly configured. Multiple developers report this on GitHub Discussions. This breaks automated tasks like nightly builds, cleanup jobs, and periodic deployments.
GitHub Actions runner issue #4210 confirms scheduled cron tasks don't trigger on self-hosted runners. Multiple people report the same problem on community discussions forum (#185024). Affects automated CI/CD pipelines relying on self-hosted infrastructure.

Quick fixes

Confirm the exact error signature matches GitHub Actions scheduled cron task does not trigger on self-hosted runner.
Check the GitHub Actions account, local tool state, and provider configuration involved in the failing workflow.
Compare the failing environment with a known working setup, then change one configuration value at a time.

Platform/tool-specific checks

Verify the command, editor, extension, or API client that produced the error.
Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
Avoid deleting credentials, local model data, or project settings until the failing scope is clear.

Step-by-step troubleshooting

Capture the exact error message and the command, editor action, or request that triggered it.
Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
Review the source evidence below and compare it with your environment.
Apply one change at a time and rerun the smallest failing action.
Keep the working fix documented for the team or deployment environment.

How to prevent it

Keep provider/tool configuration documented.
Record non-secret diagnostics such as tool version, provider name, model name, and command path.
Add a lightweight check before CI or production workflows depend on the tool.

Diagnostic flow for this page

Match GitHub Actions scheduled cron task does not trigger on self-hosted runner exactly before applying the quick fix.
Compare the failing environment with GitHub Actions versions, account scope, provider settings, and deployment context.
Check the listed common causes in order, starting with the cause that best matches your logs.
Use the evidence status below to decide whether to confirm against public sources or official documentation.
Apply one reversible change, rerun the smallest failing action, and keep rollback notes.

FAQ

What does GitHub Actions scheduled cron task does not trigger on self-hosted runner mean in GitHub Actions?

GitHub Actions scheduled cron task does not trigger on self-hosted runner indicates the workflow described by "GitHub Actions Scheduled Cron Workflows Not Triggering on Self-Hosted Runners" failed in a GitHub Actions context. Start by confirming the exact signature and the component that emitted it.

What should I check first for GitHub Actions scheduled cron task does not trigger on self-hosted runner?

Check whether this cause matches your environment: Self-hosted GitHub Actions runners don't trigger scheduled cron workflows even though the workflow YAML is correctly configured. Multiple developers report this on GitHub Discussions. This breaks automated tasks like nightly builds, cleanup jobs, and periodic deployments.

Is the GitHub Actions scheduled cron task does not trigger on self-hosted runner guidance source-backed?

The "GitHub Actions Scheduled Cron Workflows Not Triggering on Self-Hosted Runners" page is labeled source-backed. It has 2 public source URLs from github.com, so use that evidence status when deciding how much additional verification you need.

When should I avoid the quick fix for GitHub Actions scheduled cron task does not trigger on self-hosted runner?

For "GitHub Actions Scheduled Cron Workflows Not Triggering on Self-Hosted Runners", avoid applying "Compare the failing environment with a known working setup, then change one configuration value at a time." when the error text differs, the affected version or provider is different, or the change would touch credentials, billing, DNS, production deploy settings, or irreversible data.

What should I collect before debugging GitHub Actions scheduled cron task does not trigger on self-hosted runner?

For "GitHub Actions Scheduled Cron Workflows Not Triggering on Self-Hosted Runners", collect the failing GitHub Actions command or request, non-secret configuration, versions, timestamps, request IDs when available, and the smallest reproduction that still triggers the signature.