Error map
Resources exceeded during query execution BigQuery: Resources exceeded during query execution: Not enough resources for query planning - too many subqueries or query is too complex
Google Cloud / Firebase · layer 6, Platform & cloud
Centre: this error. First ring: errors it is linked with (11). 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 (11)
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…
ANR: Application Not Responding (Input dispatching timed out)
The main thread was blocked for about 5 seconds (input) or a broadcast/service took too long, so Android showed “App isn’t respon…
BigQuery: Not found: Dataset my-project:analytics was not found in location EU
BigQuery looked for the dataset in the wrong location (region) or the dataset doesn't exist.
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.
BigQuery: Quota exceeded: Your project exceeded quota for free query bytes scanned. Consider enabling billing
A free-tier/sandbox project used its monthly or daily query processing allowance.
Terraform: Error: Error creating Network: googleapi: Error 403: Compute Engine API has not been used in project 123 before or it is disabled
Terraform called a Google API that isn't enabled in the project.
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.
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…
Google API: 429 RESOURCE_EXHAUSTED — Quota exceeded for quota metric 'Read requests' and limit 'Read requests per minute per user'
Your project or user exceeded an API rate or daily quota.
BigQuery: Syntax error / Unrecognized name: customer_id at [3:8] (Did you mean customerId?)
The query references a column or alias that doesn't exist in that scope.
Terraform: Error: Attempted to load application default credentials since neither `credentials` nor `access_token` was set in the provider block. No credentials loaded
The Google provider has no credentials (ADC, service account key, impersonation).
Two steps away (29)
no space left on device (Docker / Linux)
The disk (or inode table) is full — Docker images, build cache, logs and volumes are common culprits.
HTTP 504 Gateway Timeout
A proxy or gateway waited too long for the upstream server to respond and gave up.
Cloudflare Error 524: A Timeout Occurred
Cloudflare connected to the origin, but the origin didn’t send an HTTP response within 100 seconds.
HTTP 304 Not Modified
The cached copy is still valid, so the server sends no body and the client reuses its cache.
ERROR: canceling statement due to statement timeout
A query ran longer than statement_timeout and PostgreSQL cancelled it.
ERROR: out of shared memory — HINT: You might need to increase max_locks_per_transaction.
A transaction took more locks than the lock table can hold — usually touching many tables/partitions at once.
Google Cloud: 403 This API method requires billing to be enabled. Please enable billing on project and retry
The project has no active billing account, and the API/service needs one.
Cloud SQL: failed to connect to `host=PROJECT:REGION:INSTANCE user=app database=db`: dial error (timeout) / Cloud SQL Auth Proxy: failed to connect to instance
Your app or the Cloud SQL Auth Proxy couldn't open a connection to the instance — IAM, networking or configuration.
Cloud SQL: FATAL: remaining connection slots are reserved / MySQL: ERROR 1040 (08004): Too many connections
The instance's maximum connections was reached, often because serverless instances each open their own connection pool.
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.
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.
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.
GKE/Compute: Quota 'CPUS' exceeded. Limit: 8.0 in region us-central1 (QUOTA_EXCEEDED)
Creating nodes or clusters needs more vCPUs than your project's regional quota allows.
Compute Engine: Quota 'N2_CPUS' exceeded. Limit: 24.0 in region europe-west1 / QUOTA_EXCEEDED
The project reached a regional Compute Engine quota (vCPUs per machine family, GPUs, disks, addresses).
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 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: 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.
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…
Google Cloud: Error: Could not load the default credentials. Browse to https://cloud.google.com/docs/authentication/getting-started
The Google client library found no Application Default Credentials (ADC) on this machine or environment.
GKE/Kubernetes: Pod unschedulable — 0/3 nodes are available: 3 Insufficient cpu
The scheduler found no node with enough free CPU/memory for the pod's resource requests.
kubectl: error: executable gke-gcloud-auth-plugin not found — it looks like you are trying to use a client-go credential plugin that is not installed
kubectl needs the `gke-gcloud-auth-plugin` binary to authenticate to GKE, and it is missing from PATH.
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.
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).
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.
AWS: ExpiredToken — The security token included in the request is expired
Temporary AWS credentials (STS/SSO/assumed role) have expired.
AWS: SignatureDoesNotMatch / InvalidClientTokenId — the request signature we calculated does not match
AWS rejected the request signature — wrong secret key, wrong region, clock skew, or a presigned URL used differently from how it…
UnrecognizedClientException: The security token included in the request is invalid
The access key or session token isn’t recognised — wrong/deleted key, a session token missing for temporary credentials, or a reg…
Map another error
Popular: 500403400ORA-009331064Critical errorFileNotFoundException assemblyTypeError