GitHub Actions: workflow does not run on push / pull_request / workflow_dispatch button missing
A workflow file exists but no run appears — the trigger filters do not match, the file is not on the right branch, or the workflow is disabled.
workflow not triggeringGitHub Actions workflow not runningworkflow_dispatch not showingRun workflow button missingGitHub Actions not triggered on push Meaning
There is no error message, which makes this confusing. Check, in order: the file is in .github/workflows/ on the branch GitHub reads (for workflow_dispatch and schedule the default branch), the on: events and branches/paths filters match your change, the workflow is not disabled, and commits from a workflow using GITHUB_TOKEN do not trigger other workflows.
Common causes
workflow_dispatch/schedulefile not on the default branchbranches/pathsfilters exclude the change- YAML error so the workflow never registered
- Push made with
GITHUB_TOKEN(it does not trigger new runs) - Workflow disabled (inactivity of 60 days on schedules) or Actions disabled for the repo
⚡ Quick fix
- Open Actions → the workflow → check for a "disabled" banner or YAML error
- Compare
on:filters with the files and branch you changed - Use a PAT or GitHub App token if one workflow must trigger another
Detailed fix by platform
GitHub Actions
- Minimal trigger:
on: { push: { branches: [main] }, pull_request: {}, workflow_dispatch: {} } - Merge the workflow into the default branch before using
workflow_dispatch
Code examples
Triggers that rarely miss
name: CI
on:
push:
branches: [main]
pull_request:
workflow_dispatch: # shows the "Run workflow" button (file must be on the default branch)How to diagnose
- Location — Is the file on the right branch?
- Filters — Do branches/paths match?
- State — Disabled or YAML error?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- API rate limit exceeded GitHub Actions: HttpError: API rate limit exceeded for installation ID 123456 / secondary rate limit
- Cache not found / Unable to reserve cache GitHub Actions: Cache not found for input keys: npm-Linux-abc123 / Failed to save: Unable to reserve cache with key, another job may be creating this cache
- Credentials could not be loaded GitHub Actions: Error: Credentials could not be loaded, please check your action inputs: Could not load credentials from any providers
Most viewed in CI/CD
- The process '/usr/bin/git' failed with exit code 128 GitHub Actions: Error: The process '/usr/bin/git' failed with exit code 128
- This job is stuck because you don't have any active runners GitLab CI: This job is stuck because you don't have any active runners online or available with any of these tags assigned to them
- Resource not accessible by integration GitHub Actions: Error: Resource not accessible by integration (403)
Other ways to find it
Where this error sits
Origin: Build & delivery. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 25 Oct 2026