GitHub Actions "startup_failure" - Run Never Starts
A run was created but immediately concluded as startup_failure, meaning GitHub could not even set up the run. The workflow file or one of its references is invalid before any job runs.
What this error means
A run appears in the Actions tab with conclusion startup_failure and no jobs. There are no step logs because the run never progressed past setup.
Actions tab
Run conclusion: startup_failure
# the run card shows the failure with no jobs underneathCommon causes
Invalid workflow or referenced file
A YAML/schema error in the workflow, or in a reusable workflow it calls, fails run setup and yields startup_failure.
Bad action or workflow reference
A uses: pointing at a missing action/workflow, or a malformed expression evaluated at setup, prevents the run from starting.
How to fix it
Validate the workflow and its references
Lint the workflow and every reusable workflow/action it references so setup can complete.
Terminal
actionlint .github/workflows/*.ymlInspect the run for the underlying error
- Open the startup_failure run - the annotation usually names the invalid file or reference.
- Fix the referenced workflow/action ref so it resolves.
- Re-push; a valid file produces real jobs instead of startup_failure.
How to prevent it
- Lint workflows and their references in CI before merge.
- Pin actions and reusable workflows to refs that exist.
- Keep expressions evaluated at setup valid and simple.
Related guides
GitHub Actions "This run likely failed because of ... reusable workflow"Fix GitHub Actions runs that fail pointing at a called reusable workflow - a syntax error or invalid ref in t…
GitHub Actions "No event triggers defined in 'on'"Fix GitHub Actions "No event triggers defined in `on`" - an empty, null, or malformed on: block means the wor…
GitHub Actions "Top level 'jobs' section is required"Fix GitHub Actions "The top level `jobs` section is required" - a missing, empty, or misindented jobs: block,…