Error map
Unable to process file command GitHub Actions: Error: Unable to process file command 'output' successfully. Invalid format 'x'
CI/CD · layer 7, Build & delivery
Centre: this error. First ring: errors it is linked with (8). Outer ring: what those are linked with. Colours show the layer of a request each error belongs to. Click any dot to re-centre the map on it; hover to follow its connections. The centre dot opens the error page.
Directly related (8)
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
`actions/cache` either found nothing for your key (restore miss) or could not save because another run is already saving the same…
GitHub Actions: The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files
Workflows (or old actions) still use `::set-output`, which must be replaced by writing to the `$GITHUB_OUTPUT` file.
GitHub Actions: Error: Credentials could not be loaded, please check your action inputs: Could not load credentials from any providers
`aws-actions/configure-aws-credentials` found no usable credentials — no keys, no role to assume, or the OIDC token was not reque…
GitHub Actions: Invalid workflow file: .github/workflows/ci.yml#L12 — You have an error in your yaml syntax on line 12
GitHub could not parse your workflow YAML, so no run was created — usually indentation, a tab, or an unquoted special character.
GitHub Actions: Error: Unable to process command '::set-env name=X::y' successfully. The `set-env` command is disabled
A script or old action uses `::set-env` / `::add-path`, which GitHub disabled; write to `$GITHUB_ENV` and `$GITHUB_PATH` instead.
GitHub Actions: Error: Unable to download artifact(s): Artifact not found for name: build
`download-artifact` could not find an artifact with that name in the run (or repository) — it was never uploaded, named different…
GitHub Actions: Matrix vector 'node' does not contain any values / Error when evaluating 'strategy' for job
The job's `strategy.matrix` ended up empty — a `fromJSON()` expression produced no values, or a dimension is an empty list.
GitHub Actions: HttpError: API rate limit exceeded for installation ID 123456 / secondary rate limit
Your workflow (or an action it uses) made too many GitHub API calls and was throttled with 403/429.
Two steps away (17)
npm ERR! `npm ci` can only install packages when your package.json and package-lock.json are in sync
package-lock.json doesn’t match package.json, so npm ci refuses to install.
GitHub Actions: Unrecognized named-value: 'secrets'. Located at position 1 within expression: secrets.API_KEY
You used an expression context (`secrets`, `env`, `matrix`, `steps`…) in a place of the workflow where that context is not availa…
GitHub Actions: workflow does not run on push / pull_request / workflow_dispatch button missing
A workflow file exists but no run appears — the trigger filters do not match, the file is not on the right branch, or the workflo…
GitHub Actions: Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3
A warning that actions in your workflow still run on an old Node.js runtime; update them to current major versions.
is not authorized to perform: sts:AssumeRole on resource: arn:aws:iam::...:role/...
The caller can’t assume the role — either its own policy doesn’t allow sts:AssumeRole, or the role’s trust policy doesn’t trust t…
GitHub Actions: secret is empty on pull_request from a fork or Dependabot (Secrets are not passed to workflows triggered by a fork)
Secrets are intentionally withheld from workflows that run for pull requests from forks and, by default, for Dependabot PRs — so…
GitHub Actions: Error: Input required and not supplied: token
An action needs an input (token, ssh-key, api-key…) and the `with:` value is empty or missing — often because the secret does not…
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.
GitHub Actions: Expected — Waiting for status to be reported (required check never runs on the pull request)
Branch protection requires a status check that no workflow reports for this PR, so the merge button stays blocked.
GitLab CI: Found errors in your .gitlab-ci.yml: jobs:build config contains unknown keys: scripts
GitLab rejected the pipeline configuration, so no pipeline was created — the message names the job and the problem.
WARN: the attribute `version` is obsolete, it will be ignored
A harmless Compose v2 warning: the top-level version: line in docker-compose.yml is no longer used.
GitHub Actions: Error: Process completed with exit code 1.
A `run:` command returned a non-zero status, so the step (and job) failed — the real cause is printed in the log lines above.
GitHub Actions: Error: Process completed with exit code 127 — command not found
The shell could not find the command you tried to run: it is not installed on the runner, not on PATH, or misspelled.
GitHub Actions: Error: Process completed with exit code 137 (Killed — out of memory)
The command was killed by the system with SIGKILL (128 + 9), almost always because the runner ran out of memory.
API Error: Too many concurrent requests (concurrency limit reached)
You have more requests in flight at once than the API allows for your key — even if your requests-per-minute rate is fine.
GitHub Actions: Error: Resource not accessible by integration (403)
The workflow’s GITHUB_TOKEN doesn’t have the permission needed for that API call (comment, push, create release, write packages).
GitHub Actions: The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled
The machine running your job was shut down or reclaimed while the job was running — a self-hosted runner stopped, a spot instance…
Map another error
Popular: 403500400ORA-00933Critical error1064FileNotFoundException assemblyTypeError