GitHub Actions "workflow run failed: startup_failure"

By Kaveh Alemi·Latchkey

startup_failure means GitHub could not even begin the run. The cause is either the workflow file failing to compile on that ref, or a transient backend error preparing the run.

What this error means

A run shows conclusion startup_failure with no job logs, often with no obvious step output.

The workflow run failed: startup_failure
This run could not be started. The workflow file may be invalid, or a system error occurred.

Common causes

Invalid workflow file on the triggering ref

A YAML or schema error on the branch that triggered the event prevents the run from compiling.

Transient backend error

A GitHub-side system error during run preparation produces startup_failure even with a valid file.

How to fix it

Validate the workflow on the triggering ref

1. Open the workflow file on the exact branch/ref that triggered the event and check for YAML errors.
2. Lint it locally with actionlint.
3. Fix any schema issues and push.

Re-run on transient failures

1. If the file is valid, re-run all jobs; startup_failure from a backend hiccup usually clears on retry.
2. On managed runners, Latchkey auto-retries transient startup failures so a single infra blip does not fail your pipeline.

How to prevent it

• Run actionlint in CI on workflow changes to catch invalid files before merge.
• Treat isolated startup_failure with a valid file as transient and retry.

Frequently asked questions

Related guides

References

• GitHub Actions documentation
• Workflow syntax for GitHub Actions