Skip to content
Latchkey

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 underneath

Common 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/*.yml

Inspect the run for the underlying error

  1. Open the startup_failure run - the annotation usually names the invalid file or reference.
  2. Fix the referenced workflow/action ref so it resolves.
  3. 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

Tired of flaky CI? Latchkey auto-heals failed jobs and retries them for you. Start free →