Error map
Cloud Run Jobs Cloud Run Job: Task failed — retried max-retries times and execution failed
Google Cloud / Firebase · layer 6, Platform & cloud
Centre: this error. First ring: errors it is linked with (9). 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 (9)
Job has reached the specified backoff limit (BackoffLimitExceeded)
The Job’s pods failed more times than backoffLimit (default 6), so Kubernetes marked the Job failed and stopped retrying.
Cloud Run: Memory limit of 512 MiB exceeded with 530 MiB used. Consider increasing the memory limit
The container used more memory than the Cloud Run service allows, so the instance was terminated.
Cloud Run: Error: Forbidden — Your client does not have permission to get URL / from this server
The Cloud Run service requires authentication and the caller has no valid identity token or the `roles/run.invoker` role.
Cloud Run: 503 Service Unavailable — The request was aborted because there was no available instance
Cloud Run could not serve the request: no instance was ready, instances crashed, or the service hit its max-instances/concurrency…
Cloud Functions: Function execution took 60002 ms, finished with status: 'timeout'
The function ran past its timeout (default 60s for HTTP 1st gen) and was terminated.
Cloud Run domain mapping stuck: certificate provisioning pending (CertificatePending)
A custom domain mapped to Cloud Run never gets a certificate.
Cloud Run: Container called exit(1) — the revision failed to start
The container process exited with an error right after starting, so Cloud Run marked the revision as failed.
Cloud Function runs twice or loops forever: event retries without idempotency
An event-triggered function is invoked repeatedly because it fails (with retries on) or events are delivered at least once.
Cloud Run background work stops after the response (CPU only allocated during requests)
Threads, timers or async jobs freeze or never finish because CPU is throttled outside request handling.
Two steps away (27)
Kubernetes: CrashLoopBackOff
The container starts, crashes (or exits), and Kubernetes keeps restarting it with increasing back-off delays.
Kubernetes: OOMKilled (exit code 137)
The container used more memory than its limit, and the kernel killed it.
Kubernetes: CreateContainerConfigError — secret / configmap not found
Kubernetes can’t build the container’s configuration — usually a referenced Secret, ConfigMap or key doesn’t exist in that namesp…
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.
MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 listeners added
More than 10 listeners were added to one event — often a leak where listeners are added repeatedly.
MemoryError (Unable to allocate X GiB for an array)
Python couldn’t allocate memory — the data is larger than available RAM or address space.
Cloud Run: 504 Gateway Timeout — The request has been terminated because it has reached the maximum request timeout
The request ran longer than the service's request timeout (default 5 minutes, max 60), so Cloud Run closed it.
Cloud Run: Revision 'svc-00005' is not ready — Image 'gcr.io/proj/app:latest' not found / Permission 'artifactregistry.repositories.downloadArtifacts' denied
Cloud Run cannot pull the container image — it doesn't exist, the tag is wrong, or the service identity lacks access to the regis…
GKE: google.api_core.exceptions.Forbidden: 403 Caller does not have required permission — Workload Identity: unable to generate access token
A pod tried to call Google APIs but its Kubernetes service account is not bound to a Google service account (or the binding lacks…
Cloud Run: The user-provided container failed to start and listen on the port defined provided by the PORT=8080 environment variable
Cloud Run started your container, but nothing listened on $PORT within the startup timeout — the app crashed, listens on another…
GKE Ingress: Some backend services are in UNHEALTHY state / 502 Server Error from the load balancer
The Google load balancer's health checks fail for the Ingress backends, so it returns 502 or 'no healthy upstream'.
gcloud/ADC: WARNING: Your active project does not match the quota project in your local Application Default Credentials file
Application Default Credentials bill API usage to a different project than the one you have set as active, which can cause surpri…
Go: Get "https://api.example.com": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
An operation did not finish before its context deadline or HTTP client timeout.
Google Cloud: 403 SERVICE_DISABLED — Cloud Resource Manager API has not been used in project 123456 before or it is disabled. Enable it by visiting
The Google API you called is not enabled for the project that the request is billed to.
Pub/Sub: Messages keep being redelivered — acknowledgement deadline expired before the subscriber acked
Your subscriber took longer than the ack deadline to acknowledge, so Pub/Sub redelivered the message (duplicate processing).
net::ERR_NAME_NOT_RESOLVED (This site can't be reached — server IP address could not be found)
DNS couldn’t resolve the hostname in the browser.
ACM certificate stuck in Pending validation
ACM is waiting to see the DNS (or email) validation record — it wasn’t created, was created in the wrong DNS zone, or has a typo.
dial tcp: lookup registry-1.docker.io: no such host / Temporary failure in name resolution during docker build
DNS isn’t working for the Docker daemon or inside build containers, so pulls and package downloads fail.
[nodemon] app crashed - waiting for file changes before starting...
Your app threw an error on startup; nodemon is waiting for a file change to retry.
Docker container exits immediately (Exited (0) / Exited (1) right after start)
The container started and its main process finished at once, so the container stopped — Docker containers only live as long as PI…
Docker container keeps restarting (Restarting (1) x seconds ago)
The container crashes on start and its restart policy (always/unless-stopped/on-failure) starts it again in a loop.
Error: Unhandled 'error' event (events.js / node:events)
An EventEmitter (stream, socket, child process, server) emitted 'error' and nothing listened for it, so Node crashed.
Cloud Functions: Provided module can't be loaded / Function failed on loading user code. This is likely due to a bug in the user code
The function started but could not import/initialise your code, so every invocation fails.
Cloud Functions: Build failed: function.js does not exist / npm install failed with exit code 1 (Cloud Build step)
The deployment's build step (Cloud Build) failed, so no new function version was created.
Cloud Run: Startup probe failed — revision not ready (container didn't become healthy in time)
The configured startup probe never succeeded, so Cloud Run stopped waiting for the container.
Cloud Run: The request was aborted because there was no available instance (HTTP 429)
All instances were busy (at max concurrency or max instances) and a new one couldn't start in time.
Cloud Run deploy failed: Permission denied on secret (secretmanager.versions.access)
The service account can't read the secret that is mounted as an env var or volume.
Map another error
Popular: 5004004031064ORA-00933Critical errorFileNotFoundException assemblyTypeError