Error map
timeout while waiting for state to become 'available' Terraform: Error: waiting for RDS DB Instance create: timeout while waiting for state to become 'available' (last state: 'creating', timeout: 40m0s)
Terraform · layer 6, Platform & cloud
Centre: this error. First ring: errors it is linked with (12). 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 (12)
AWS Lambda: Task timed out after X seconds
The function ran longer than its configured timeout (default 3 seconds) and Lambda stopped it.
API Gateway: {"message": "Endpoint request timed out"} (504 after 29 seconds)
The backend (usually Lambda) didn’t respond within API Gateway’s integration timeout (29 seconds by default for REST APIs).
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.
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.
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.
Terraform: # aws_instance.web is tainted, so must be replaced — -/+ destroy and then create replacement
A previous apply failed during creation, so Terraform marked the resource tainted and will recreate it.
Terraform: Error: Invalid AWS Region: us-east-3 / Error: configuring Terraform AWS Provider: validating provider credentials: operation error STS: GetCallerIdentity
The `region` is invalid/unavailable, or the provider can't reach AWS endpoints to validate credentials.
Terraform: Error: creating S3 Bucket (my-bucket): BucketAlreadyOwnedByYou / EntityAlreadyExists: Role with name x already exists
The resource exists outside Terraform's state (created manually or by another stack), so create fails.
Terraform: Error: local-exec provisioner error — Error running command './deploy.sh': exit status 1. Output: ...
A `local-exec`/`remote-exec` provisioner command failed, so the resource is marked tainted.
Terraform: Error: deleting EC2 VPC (vpc-0abc): DependencyViolation: The vpc 'vpc-0abc' has dependencies and cannot be deleted
Destroy failed because something else still uses the resource (ENIs, subnets, gateways, security group rules).
Terraform: Error: Provider produced inconsistent result after apply — When applying changes to aws_x.y, provider produced an unexpected new value: Root resource was present, but now absent
After creating/updating a resource, the provider returned values that don't match what Terraform planned — usually a provider bug…
Terraform: Error: No valid credential sources found — failed to refresh cached credentials, no EC2 IMDS role found / Error: configuring Terraform AWS Provider: no valid credential sources
The AWS provider found no credentials (env vars, shared config, SSO, role, instance profile).
Two steps away (32)
AWS: ThrottlingException / Rate exceeded
You exceeded the request rate for an AWS API; retry with exponential backoff.
HTTP 504 Gateway Timeout
A proxy or gateway waited too long for the upstream server to respond and gave up.
java.util.concurrent.TimeoutException
A Future.get(timeout) or async operation didn’t complete in the allowed time.
MySQL ERROR 2006 (HY000): MySQL server has gone away
The connection to MySQL was closed — usually by a timeout or a packet larger than `max_allowed_packet`.
HTTP 408 Request Timeout
The server closed the connection because the client took too long to send the complete request.
HTTP 499 Client Closed Request (Nginx)
Nginx-specific code logged when the client disconnected before the server finished responding.
CircleCI: Error calling workflow: 'build'. Cannot find a definition for job named test / Config does not conform to schema
CircleCI could not compile `.circleci/config.yml` — a workflow refers to a missing job, a key is invalid, or the YAML is malforme…
CircleCI: Cannot find orb 'circleci/node@9.9.9'. Check the namespace and version exist
The orb reference in your config does not resolve: wrong namespace, name or version, or the orb is private and not accessible.
Azure Pipelines: /azure-pipelines.yml: File /templates/build.yml not found in repository / Unable to find template
The YAML references a template (`template: templates/build.yml`) that Azure cannot find — wrong path, repo resource or branch.
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…
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: 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…
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.
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: 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.
Terraform: Error: Backend configuration changed — A change in the backend configuration has been detected, which may require migrating existing state
The saved backend settings in `.terraform` differ from the current configuration.
Terraform: Error: Cannot import non-existent remote object — While attempting to import an existing object to "aws_s3_bucket.logs", the provider detected that no object exists with the given id
`terraform import` (or an import block) used an ID that the provider can't find.
Terraform: Error: Instance cannot be destroyed — Resource aws_db_instance.prod has lifecycle.prevent_destroy set, but the plan calls for this resource to be destroyed
The plan would destroy a resource protected with `lifecycle { prevent_destroy = true }`.
S3 PermanentRedirect: The bucket you are attempting to access must be addressed using the specified endpoint
The request went to the wrong S3 region/endpoint for that bucket.
InvalidKeyPair.NotFound: The key pair 'x' does not exist
The key pair name you passed doesn’t exist in that region (key pairs are regional).
InvalidAMIID.NotFound: The image id '[ami-xxxx]' does not exist
The AMI ID isn’t available in this region/account — AMI IDs are regional and private AMIs must be shared.
Error from server (AlreadyExists): ... already exists
kubectl create tried to make an object whose name is already taken in that namespace.
The Deployment is invalid: spec.selector: Invalid value: field is immutable
You tried to change a field Kubernetes doesn’t allow to change after creation — Deployment selectors, Job templates, Service clus…
strict decoding error: unknown field "spec.template.spec.containers[0].ports[0].protocl"
The manifest contains a field the API schema doesn’t know — a typo, wrong indentation, or a field from another API version.
Terraform: Error: creating EC2 Instance: UnauthorizedOperation: You are not authorized to perform this operation. User: arn:aws:iam::123:user/ci is not authorized to perform: ec2:RunInstances
The IAM identity used by Terraform lacks a permission needed for that resource.
Terraform: Error: Cycle: aws_security_group.a, aws_security_group.b
Resources reference each other (directly or indirectly), so Terraform can't order them.
Terraform: Error: deleting S3 Bucket (my-bucket): BucketNotEmpty: The bucket you tried to delete is not empty
Terraform can't delete an S3 bucket that still holds objects (or versions).
Terraform: Error: reading EC2 Instance (i-0abc): couldn't find resource / 404 ResourceNotFound during refresh
A resource tracked in state no longer exists in the cloud (deleted manually) or can't be read with current credentials.
Terraform: Error: Provider produced invalid plan — provider produced an invalid plan for aws_x.y, but we are tolerating it because it is using the legacy plugin SDK
The provider changed planned values between plan and apply (a provider bug), so Terraform aborts.
AWS: ExpiredToken — The security token included in the request is expired
Temporary AWS credentials (STS/SSO/assumed role) have expired.
AWS: Unable to locate credentials / Could not load credentials from any providers
The AWS CLI/SDK found no credentials in any place it looks — env vars, profile files, SSO cache or an instance/task role.
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…
Map another error
Popular: 500403400ORA-009331064Critical errorFileNotFoundException assemblyTypeError