CircleCI: Error calling workflow: 'build'. Cannot find a definition for job named test / Config does not conform to schema
CircleCI could not compile .circleci/config.yml — a workflow refers to a missing job, a key is invalid, or the YAML is malformed.
Cannot find a definition for job namedConfig does not conform to schemaError calling workflowUnexpected argument(s) CircleCI configConfig compilation failed CircleCI Meaning
Use the CircleCI CLI to validate locally: circleci config validate. Errors name the workflow, job or key. Make sure version: 2.1, jobs referenced in workflows exist, orbs are declared, and parameters have the right types.
Common causes
- Workflow
jobs:references a job that is not defined - Misspelled key or wrong nesting
- Using 2.1 features (orbs, parameters) with
version: 2 - Parameter type mismatch
- YAML indentation error
⚡ Quick fix
- Run
circleci config validatebefore pushing - Match job names between
jobs:andworkflows: - Use
version: 2.1for orbs and parameters
Detailed fix by platform
CircleCI
- Install the CLI and validate:
circleci config validate .circleci/config.yml - Preview the expanded config:
circleci config process .circleci/config.yml
Code examples
Matching job and workflow
version: 2.1
jobs:
test:
docker: [{ image: cimg/node:20.11 }]
steps: [checkout, { run: npm test }]
workflows:
main:
jobs: [test]How to diagnose
- Validate — circleci config validate output?
- Names — Workflow jobs defined?
- Version — 2.1 used?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- .gitlab-ci.yml invalid GitLab CI: Found errors in your .gitlab-ci.yml: jobs:build config contains unknown keys: scripts
- Cannot find orb CircleCI: Cannot find orb 'circleci/node@9.9.9'. Check the namespace and version exist
- ComparisonError: manifest generation failed Argo CD: ComparisonError: rpc error: code = Unknown desc = Manifest generation error (cached): kustomize build failed
Most viewed in CI/CD
- The process '/usr/bin/git' failed with exit code 128 GitHub Actions: Error: The process '/usr/bin/git' failed with exit code 128
- This job is stuck because you don't have any active runners GitLab CI: This job is stuck because you don't have any active runners online or available with any of these tags assigned to them
- Resource not accessible by integration GitHub Actions: Error: Resource not accessible by integration (403)
Other ways to find it
Where this error sits
Origin: Build & delivery. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 25 Oct 2026