error parsing called workflow CI/CD Origin: Build & delivery Last updated 25 Oct 2026

GitHub Actions: error parsing called workflow ".github/workflows/ci.yml" -> "org/repo/.github/workflows/build.yml@main": workflow was not found

A job calls a reusable workflow (uses: org/repo/.github/workflows/x.yml@ref) that GitHub cannot find or is not allowed to use.

Exact message you may see error parsing called workflowworkflow was not foundinvalid value workflow referenceerror parsing called workflow ".github/workflowsworkflow is not reusable
Explore the map of this error Full error map →
Seen on: GitHub Actions

Meaning

The path, repository, ref, visibility and access settings must all match. The called file must be under .github/workflows/ and have on: workflow_call. Private repositories must allow access from other repositories (Settings → Actions → General → Access). Local calls use ./.github/workflows/x.yml without @ref.

Common causes

  • Wrong path, repository or ref (branch/tag/SHA) in uses:
  • Called workflow lacks on: workflow_call
  • Private repository not shared with other repositories
  • Local reusable workflow written with @main
  • Called workflow file YAML invalid

⚡ Quick fix

  1. Open the exact path and ref in the browser to verify
  2. Add on: workflow_call: (with inputs/secrets) to the called file
  3. Enable access for repositories in the called repo's Actions settings

Detailed fix by platform

GitHub Actions

  1. Same repo: uses: ./.github/workflows/build.yml
  2. Other repo: uses: org/shared/.github/workflows/build.yml@v1 with secrets: inherit

Code examples

Caller and callee

yaml
# called workflow: .github/workflows/build.yml
on:
  workflow_call:
    inputs: { node: { type: string, default: '20' } }

# caller
jobs:
  build:
    uses: ./.github/workflows/build.yml
    with: { node: '22' }

How to diagnose

  1. Reference — Path, repo and ref correct?
  2. Trigger — workflow_call present?
  3. Access — Repo allows external callers?

🔧 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…Cache not found / Unable to reserve cache — GitHub Actions: Cache not found for input keys: npm-Linux-abc123 / Failed to save: Unable to reserve cache with key, another job may be creating this cache (CI/CD)Cache not found / Una…Cannot find orb — CircleCI: Cannot find orb 'circleci/node@9.9.9'. Check the namespace and version exist (CI/CD)Cannot find orbComparisonError: manifest generation failed — Argo CD: ComparisonError: rpc error: code = Unknown desc = Manifest generation error (cached): kustomize build failed (CI/CD)ComparisonError: mani…Credentials could not be loaded — GitHub Actions: Error: Credentials could not be loaded, please check your action inputs: Could not load credentials from any providers (CI/CD)Credentials could not…Input required and not supplied — GitHub Actions: Error: Input required and not supplied: token (CI/CD)Input required and no…Invalid workflow file — GitHub Actions: Invalid workflow file: .github/workflows/ci.yml#L12 — You have an error in your yaml syntax on line 12 (CI/CD)Invalid workflow fileTemplate 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…error par…

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.