state snapshot was created by a newer Terraform version Terraform Origin: Platform & cloud OSI layer 7 · Application Last updated 5 Nov 2026

Terraform: Error: state snapshot was created by Terraform v1.9.0, which is newer than current v1.6.6; upgrade to Terraform v1.9.0 or greater to work with this state

The remote/local state was last written by a newer Terraform CLI than the one you're running.

Exact message you may see Error: state snapshot was created by Terraform v1.9.0, which is newer than current v1.6.6state snapshot was created by Terraform which is newer than currentupgrade to Terraform v1.9.0 or greater to work with this stateError: Failed to load state: state snapshot was created byTerraform state version newer than CLI
Explore the map of this error Full error map →
Seen on: Terraform

Meaning

Upgrade your Terraform to at least that version (state format changes aren't backward compatible). Don't try to edit the state version manually. Standardise versions across the team/CI before one person upgrades, because the first apply with a newer CLI updates the state version.

Common causes

  • A teammate/CI used a newer Terraform
  • Local CLI outdated
  • Mixed CI images
  • State migrated by an upgrade
  • Multiple tools (OpenTofu vs Terraform) writing state

⚡ Quick fix

  1. Upgrade CLI to the version named (tfenv install 1.9.0)
  2. Pin the version in CI and docs
  3. Coordinate upgrades (apply once with the new version everywhere)

Detailed fix by platform

Terraform

  1. terraform version; tfenv install 1.9.0 && tfenv use 1.9.0

How to diagnose

  1. State — Written by?
  2. CLI — Older?
  3. Policy — Pinned?

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: Platform & cloud. Errors that are often confused with or caused by this one (click to open):

Backend configuration changed (migrate or reconfigure) — Terraform: Error: Backend configuration changed — A change in the backend configuration has been detected, which may require migrating existing state (Terraform)Backend configuration…Backend initialization required — Terraform: Error: Backend initialization required, please run "terraform init" — Reason: Initial configuration of the requested backend "s3" (Terraform)Backend initializatio…Cannot import non-existent remote object — 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)Cannot import non-exi…client version is too new — Error response from daemon: client version 1.45 is too new. Maximum supported API version is 1.41 (Docker)client version is too…Error acquiring the state lock — Terraform: Error: Error acquiring the state lock — ConditionalCheckFailedException / state blob is already locked (Terraform)Error acquiring the s…Invalid target address / No matching objects found (state commands) — Terraform: Error: Invalid target address — No matching objects found. To view the available instances, use "terraform state list" (Terraform)Invalid target addres…Provider configuration not present (removed resource) — Terraform: Error: Provider configuration not present — its original provider configuration is required, but it has been removed (Terraform)Provider configuratio…Unsupported Terraform Core version — Terraform: Error: Unsupported Terraform Core version — This configuration does not support Terraform version 1.5.7 (Terraform)Unsupported Terraform…state sna…

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.