Error map
The runner has received a shutdown signal 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
CI/CD · layer 7, Build & delivery
Centre: this error. First ring: errors it is linked with (10). 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 (10)
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: 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…
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
No GitLab runner can pick up the job — runners are offline, the job’s tags don’t match any runner, or shared runners are disabled.
GitHub Actions: The job running on runner GitHub Actions 12 has exceeded the maximum execution time of 360 minutes
A job ran longer than its time limit — your `timeout-minutes`, or the 6-hour (360 minute) platform limit — and was cancelled.
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.
GitHub Actions: System.IO.IOException: No space left on device — the runner's disk is full
The job filled the runner's disk (about 14 GB free on standard Linux runners): large Docker images, caches, build outputs or test…
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: Waiting for a runner to pick up this job… (job stays queued — No runner matching the specified labels)
The job is queued and never starts — no available runner has all the labels in `runs-on`, runners are offline/busy, or the hosted…
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.
GitLab CI: ERROR: Registering runner... failed runner=abc status=couldn't execute POST against https://gitlab.com/api/v4/runners: 403 Forbidden
`gitlab-runner register` was rejected — the registration token is invalid or expired, or GitLab now expects an authentication tok…
Two steps away (26)
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: 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…
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: 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: 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.
Azure Pipelines: No hosted parallelism has been purchased or granted
The Azure DevOps organization has no Microsoft-hosted parallel jobs, so pipelines can’t run on hosted agents.
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: Error: The process '/usr/bin/git' failed with exit code 128
A git command inside the workflow failed — usually authentication to a private repo/submodule, a missing ref, or pushing without…
GitLab CI: ERROR: Job failed: execution took longer than 1h0m0s seconds
The job ran past its timeout (project default is 60 minutes) and GitLab killed it.
CircleCI: Too long with no output (exceeded 10m0s): context deadline exceeded
A CircleCI step printed nothing for 10 minutes, so CircleCI assumed it hung and cancelled it.
Kubernetes: OOMKilled (exit code 137)
The container used more memory than its limit, and the kernel killed it.
FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
The V8 heap hit its limit — a large build (webpack, tsc, Next.js) needs more memory, or the app leaks.
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.
Docker build slow: "Sending build context to Docker daemon 2.5GB" / transferring context takes forever
docker build is uploading your whole project folder — node_modules, .git, data files — before building, because there’s no (or a…
GitLab CI: ERROR: Uploading artifacts as "archive" to coordinator... too large archive id=123 responseStatus=413 Request Entity Too Large
The job produced an artifact bigger than the instance or project's maximum artifact size.
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: 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: Failed to create deployment (status: 404) — Ensure GitHub Pages has been enabled
The Pages deploy step cannot create a deployment because Pages is not enabled for the repository, or is not set to "GitHub Action…
Jenkins: Still waiting to schedule task — Waiting for next available executor / 'agent1' is offline
A Jenkins build is queued because no executor with the required label is free or the agent is offline.
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: 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 process file command 'output' successfully. Invalid format 'x'
A line written to `$GITHUB_OUTPUT`, `$GITHUB_ENV` or `$GITHUB_STATE` is not in `name=value` form — usually a multi-line value wit…
GitLab CI: Cannot connect to the Docker daemon at tcp://docker:2375. Is the docker daemon running?
A docker-in-docker job could not reach the `docker:dind` service — it is not started, not privileged, or the TLS/host settings do…
GitLab CI: ERROR: Job failed: failed to pull image "registry.example.com/app:latest" with specified policies [always]: access forbidden
The runner could not pull the job's Docker image — authentication, a wrong name or tag, or a registry rate limit.
Map another error
Popular: 500403400ORA-009331064Critical errorFileNotFoundException assemblyTypeError