hashicorp/terraform · error

error loading state: %w

Error message

error loading state: %w

What it means

In LocalRun (backend_context.go:42-46), the call to b.StateMgr(op.Workspace) returned diagnostics with errors. StateMgr is responsible for constructing the remote state manager (which involves fetching the workspace, locking setup, etc.); when it fails to build the manager, the wrapped error propagates. This is a state-infrastructure failure, not a data-content failure.

Source

Thrown at internal/cloud/backend_context.go:44

func (b *Cloud) LocalRun(ctx context.Context, op *backendrun.Operation) (*backendrun.LocalRun, statemgr.Full, tfdiags.Diagnostics) {
	var diags tfdiags.Diagnostics
	ret := &backendrun.LocalRun{
		PlanOpts: &terraform.PlanOpts{
			Mode:    op.PlanMode,
			Targets: op.Targets,
		},
	}

	op.StateLocker = op.StateLocker.WithContext(ctx)

	// Get the remote workspace name.
	remoteWorkspaceName := b.getRemoteWorkspaceName(op.Workspace)

	// Get the latest state.
	log.Printf("[TRACE] cloud: requesting state manager for workspace %q", remoteWorkspaceName)
	stateMgr, sDiags := b.StateMgr(op.Workspace)
	if sDiags.HasErrors() {
		diags = diags.Append(fmt.Errorf("error loading state: %w", sDiags.Err()))
		return nil, nil, diags
	}

	log.Printf("[TRACE] cloud: requesting state lock for workspace %q", remoteWorkspaceName)
	if diags := op.StateLocker.Lock(stateMgr, op.Type.String()); diags.HasErrors() {
		return nil, nil, diags
	}

	defer func() {
		// If we're returning with errors, and thus not producing a valid
		// context, we'll want to avoid leaving the remote workspace locked.
		if diags.HasErrors() {
			diags = diags.Append(op.StateLocker.Unlock())
		}
	}()

	log.Printf("[TRACE] cloud: reading remote state for workspace %q", remoteWorkspaceName)
	if err := stateMgr.RefreshState(); err != nil {

View on GitHub (pinned to c9def3e214)

Solutions

1. Examine the wrapped diagnostic (sDiags.Err()) for the root cause; it usually reveals workspace-access or API errors.
2. Verify the cloud block organization/workspace/tags resolve correctly (see fetchWorkspace errors 484/485).
3. Re-run `terraform init` to reconfigure the backend and refresh credentials.
4. Confirm the token has read + lock permissions on the target workspace.

// Pre-flight: construct the state manager separately and report.
sm, diags := b.StateMgr(ws)
if diags.HasErrors() { return diags }

// Surface the wrapped root cause for StateMgr failures.
if sDiags.HasErrors() {
    return structuredStateError("manager-construction", sDiags.Err())
}

When it happens

Trigger: b.StateMgr(op.Workspace) at backend_context.go:42 returns sDiags with HasErrors(). Occurs during a local-run path (forcing ops locally on a cloud-configured workspace) when the state manager could not be constructed.

Common situations: Workspace not found / no access (deeper stack frames). Locking preconditions unmet. Token/API issues surfacing through StateMgr. Cloud block misconfiguration that prevents resolving the workspace.

Related errors

• Failed to retrieve workspace %s: %v
• Remote workspace Terraform version %q does not match local T
• failed checking for existing remote state: %s
• failed to generate initial lineage: %v
• failed to read state: %w

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