hashicorp/terraform · error

Failed to load state: %s

Error message

Failed to load state: %s

What it means

Wrapped error from OutputCommand after b.StateMgr(env) returns diagnostics with errors. StateMgr constructs the state manager for the selected workspace (local file, S3, cloud, etc.); a diagnostic error here means the backend could not initialize the state store for that workspace. 'terraform output' therefore has no state to read root output values from.

Source

Thrown at internal/command/output.go:88

	}

	// Command can be aborted by interruption signals
	ctx, done := c.InterruptibleContext(c.CommandContext())
	defer done()

	// This is a read-only command
	c.ignoreRemoteVersionConflict(b)

	env, err := c.Workspace()
	if err != nil {
		diags = diags.Append(fmt.Errorf("Error selecting workspace: %s", err))
		return nil, diags
	}

	// Get the state
	sMgr, sDiags := b.StateMgr(env)
	if sDiags.HasErrors() {
		diags = diags.Append(fmt.Errorf("Failed to load state: %s", sDiags.Err()))
		return nil, diags
	}

	output, err := sMgr.GetRootOutputValues(ctx)
	if err != nil {
		return nil, diags.Append(err)
	}

	return output, diags
}

func (c *OutputCommand) Help() string {
	helpText := `
Usage: terraform [global options] output [options] [NAME]

  Reads an output variable from a Terraform state file and prints
  the value. With no additional arguments, output will display all
  the outputs for the root module.  If NAME is not specified, all

View on GitHub (pinned to c9def3e214)

Solutions

1. Check the wrapped diagnostic: confirm backend resource (bucket, workspace) exists and credentials are valid.
2. Run 'terraform init' to reconfigure the backend and surface any auth errors.
3. Verify the workspace name is correct for the backend (e.g. cloud workspace exists).
4. Ensure state file / lock resources are present and writable for local/S3 backends.

Example fix

// before: backend state manager init failed
// after: re-init and confirm backend
$ terraform init
$ AWS_REGION=us-east-1 terraform output  # ensure correct creds/region

// Pre-flight: for remote backends, confirm the backend resource exists before 'terraform output'
package main

// (illustrative for S3 backend) 
func preflightS3State(bucket, key string) error {
	sess := session.Must(session.NewSession())
	svc := s3.New(sess)
	_, err := svc.HeadObject(&s3.HeadObjectInput{Bucket: &bucket, Key: &key})
	if err != nil { return fmt.Errorf("state object unreachable: %w", err) }
	return nil
}

When it happens

Trigger: Running 'terraform output' where the configured backend fails to build its state manager — e.g. S3 bucket missing, DynamoDB lock table gone, cloud backend auth failed, local state file path unwritable, or remote workspace does not exist.

Common situations: Backend credentials expired or were revoked; the S3 bucket / state object was deleted out-of-band; workspace name typo against a cloud backend that requires the workspace to pre-exist; local state file locked or permission denied; region misconfiguration.

Related errors

• Error selecting workspace: %s
• error loading state: %w
• error selecting workspace: %s
• default workspace not supported You can create a new workspa
• workspaces not supported

AI-assisted analysis of hashicorp/terraform@c9def3e214 (2026-08-07). Data as JSON: /api/errors/f4ede74022db30bf. Report an issue: GitHub.