Cannot find orb CI/CD Origin: Build & delivery Last updated 25 Oct 2026

CircleCI: Cannot find orb 'circleci/node@9.9.9'. Check the namespace and version exist

The orb reference in your config does not resolve: wrong namespace, name or version, or the orb is private and not accessible.

Exact message you may see Cannot find orbCannot find orb 'circleci/node@Orb not found CircleCIorb version does not exist
Explore the map of this error Full error map →
Seen on: CircleCI

Meaning

Orbs are referenced as namespace/name@version. Check the orb registry for the exact name and the available versions. Third-party orbs may need to be allowed in Organization Settings → Security. Private orbs require your organization to own them.

Common causes

  • Wrong namespace, orb name or version
  • Orb unpublished or version removed
  • Third-party orbs disabled for the organization
  • Orb is private to another namespace
  • Typo in orbs: mapping

⚡ Quick fix

  1. Look up the orb and a valid version in the registry
  2. Allow uncertified orbs in Organization Settings
  3. Pin to an existing version or use @volatile temporarily

Detailed fix by platform

CircleCI

  1. circleci orb info circleci/node lists versions

Code examples

Orb declaration

yaml
version: 2.1
orbs:
  node: circleci/node@5.2.0
jobs:
  build:
    executor: { name: node/default, tag: '20.11' }
    steps: [checkout, node/install-packages]

How to diagnose

  1. Name — Namespace/name correct?
  2. Version — Exists?
  3. Access — Allowed for the org?

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: Build & delivery. Errors that are often confused with or caused by this one (click to open):

API rate limit exceeded — GitHub Actions: HttpError: API rate limit exceeded for installation ID 123456 / secondary rate limit (CI/CD)API rate limit exceed…ComparisonError: manifest generation failed — Argo CD: ComparisonError: rpc error: code = Unknown desc = Manifest generation error (cached): kustomize build failed (CI/CD)ComparisonError: mani…Config compilation failed — CircleCI: Error calling workflow: 'build'. Cannot find a definition for job named test / Config does not conform to schema (CI/CD)Config compilation fa…Container exceeded memory limit — Bitbucket Pipelines: Container 'Build' exceeded memory limit / Docker container exited with code 137 (CI/CD)Container exceeded me…error parsing called workflow — GitHub Actions: error parsing called workflow ".github/workflows/ci.yml" -> "org/repo/.github/workflows/build.yml@main": workflow was not found (CI/CD)error parsing called …Template file not found — Azure Pipelines: /azure-pipelines.yml: File /templates/build.yml not found in repository / Unable to find template (CI/CD)Template file not fou…Too long with no output — CircleCI: Too long with no output (exceeded 10m0s): context deadline exceeded (CI/CD)Too long with no outp…Cannot fi…

Explore the map of this error Full error map →

🧠 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.