CircleCI "Skipping pipeline: config has errors" message
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.
CircleCI
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
- Expand the error list on the skipped pipeline.
- Fix each schema, YAML, or reference error it names.
- 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.
Terminal
circleci config validate
circleci config process .circleci/config.ymlHow 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.
Related guides
CircleCI "Config does not conform to schema" errorFix CircleCI "Config does not conform to schema" - the YAML parses but a key is unknown, mistyped, or has the…
CircleCI "Could not find a usable config" errorFix CircleCI "Could not find a usable config.yml" - CircleCI cannot locate or read .circleci/config.yml at th…
CircleCI "config has no workflows" / no jobs runFix CircleCI pipelines where no jobs run because the config defines no workflows - in 2.1 every job must be r…