Error map
Eventarc Cloud Functions (2nd gen) deploy failed: Eventarc trigger permission denied
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)
BigQuery: Access Denied: Project my-project: User does not have bigquery.jobs.create permission in project my-project
The principal can read data but is not allowed to run query jobs in the project used for billing.
Google Cloud: 403 PERMISSION_DENIED — Permission 'storage.objects.get' denied on resource (or it may not exist)
The caller's identity lacks the IAM permission named in the message on that resource.
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.
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.
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: 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 Functions: Memory limit of X MiB exceeded — function killed
The function used more memory than allocated, so the instance was terminated and the request failed.
Cloud Functions deploy: Could not upload source — storage bucket permission denied
The deploy can't stage the source ZIP in the gcf-sources bucket.
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.
Two steps away (27)
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.
GCP: FAILED_PRECONDITION: Key creation is not allowed on this service account (constraints/iam.disableServiceAccountKeyCreation)
An organisation policy forbids creating downloadable JSON keys for service accounts.
gcloud: ERROR: (gcloud.auth.print-access-token) There was a problem refreshing your current auth tokens: Reauthentication failed. cannot prompt during non-interactive execution
Your cached Google credentials expired or require a fresh login (session control or password change), and gcloud can't prompt.
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
The docker CLI can’t talk to the Docker engine — it isn’t running, or your user can’t access the socket.
OAuth 2.0 Error: invalid_scope / insufficient_scope
The requested scope is unknown or not allowed for this client — or the token lacks the scope the API endpoint requires.
Error: listen EACCES: permission denied 0.0.0.0:80
Node isn’t allowed to bind that port — ports below 1024 need root on Linux/macOS, and some Windows ports are reserved.
COPY failed: file not found in build context / "/app/x": not found
The Dockerfile COPY refers to a path outside the build context, excluded by .dockerignore, or relative to the wrong directory.
Error: error:0308010C:digital envelope routines::unsupported
An old build tool (webpack 4, old react-scripts) uses a hash algorithm that OpenSSL 3 in Node 17+ disables.
Error: @prisma/client did not initialize yet. Please run "prisma generate"
The generated Prisma Client is missing or out of date.
Service has no endpoints (no endpoints available for service / Endpoints: <none>)
The Service’s selector matches no ready pods, so traffic to it is refused or returns 503.
spec.ports[0].nodePort: Invalid value: 80: provided port is not in the valid range. The range of valid ports is 30000-32767
A NodePort Service asked for a port outside the cluster’s NodePort range (default 30000–32767).
Context.startForegroundService() did not then call Service.startForeground() / ForegroundServiceStartNotAllowedException
A foreground service didn’t call startForeground() within a few seconds, or the app tried to start one from the background where…
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…
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…
Docker push: denied: Permission "artifactregistry.repositories.uploadArtifacts" denied on resource "projects/p/locations/l/repositories/r"
Your identity cannot push or pull images in that Artifact Registry repository, or Docker isn't authenticated to the registry host.
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.
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.
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).
Kubernetes: OOMKilled (exit code 137)
The container used more memory than its limit, and the kernel killed it.
Segmentation fault (core dumped)
A program accessed memory it wasn’t allowed to, and the kernel killed it with SIGSEGV (exit code 139).
Killed / Out of memory: Killed process (Linux OOM killer)
The kernel ran out of memory and killed a process to recover — the program just prints “Killed” (exit code 137).
Cloud Storage: 403 Forbidden — user@example.com does not have storage.objects.get access to the Google Cloud Storage object
The identity making the request has no read permission on that bucket or object.
Cloud Functions: Error: Cannot find module 'X' (dependency missing at runtime)
The deployed function can't load a module that works locally.
Cloud Functions Python: ModuleNotFoundError: No module named 'X' (requirements.txt)
The deployed Python function imports a package that wasn't installed from requirements.txt.
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.
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.
Firestore: 4 DEADLINE_EXCEEDED: Deadline exceeded / 14 UNAVAILABLE: The service is currently unavailable
A Firestore request timed out or could not reach the service — contention, hot documents, large operations or network issues.
Map another error
Popular: 500400403ORA-009331064Critical errorFileNotFoundException assemblyTypeError