CircleCI "Skipping pipeline: config has errors" message

By Daniel Zoghalchali·Latchkey

A commit was pushed but no pipeline ran. CircleCI compiled .circleci/config.yml, found errors, and skipped the pipeline entirely. The compile errors are shown on the pipeline summary, not in a job log.

What this error means

The CircleCI UI shows "Skipping pipeline: the configuration file for this project has errors" with no jobs, and an expandable list of config compilation errors.

Skipping pipeline: the configuration file for this project has errors.
 * Config does not conform to schema:
   - In job 'deploy': missing required key [steps]

Common causes

config.yml failed to compile

A schema, YAML, or reference error means CircleCI cannot build a valid pipeline, so it skips rather than running a broken one.

A reusable config or orb error on this branch

An orb that failed to resolve, or a bad parameter, can make the whole config invalid on the pushed branch.

How to fix it

Read and fix the listed compile errors

1. Expand the error list on the skipped pipeline.
2. Fix each schema, YAML, or reference error it names.
3. Push again so a valid config compiles into a pipeline.

Reproduce the compile locally

Validate and process the config so you fix every error before pushing.

circleci config validate
circleci config process .circleci/config.yml

How to prevent it

• Validate config in a pre-push hook so broken pipelines never reach CircleCI.
• Pin orb versions so a moving orb does not break compilation.
• Review compiled output for reusable config changes.

Frequently asked questions

Related guides

References

• GitHub Actions documentation