Skip to content
Latchkey

Terraform Cloud "Currently HCP Terraform does not support ..." in CI

Some CLI operations do not apply to a workspace backed by the cloud block. HCP Terraform rejects them with "Currently HCP Terraform does not support ..." because the operation only makes sense for a local backend or a different execution mode.

What this error means

A CLI command fails with "Error: Currently HCP Terraform does not support" followed by the specific operation, argument, or flag that is not allowed remotely.

terraform
Error: Currently HCP Terraform does not support the -target option for plan.

The remote backend does not accept -target for runs in this workspace.

Common causes

The operation is unsupported on remote runs

Certain flags or commands (some -target uses, specific state operations) are not available when execution happens on HCP Terraform.

Execution mode mismatches the operation

An operation that assumes local execution does not translate to a Remote or Agent execution workspace.

How to fix it

Use a supported workflow

  1. Read exactly which operation the error names.
  2. Replace it with the supported remote equivalent, or drop the unsupported flag.
  3. Re-run with the standard plan/apply flow.

Switch execution mode if the operation is essential

If you genuinely need local-only behavior, set the workspace to Local execution so the CLI runs it on the runner.

Terminal
# HCP Terraform: Workspace > Settings > General > Execution Mode: Local

How to prevent it

  • Prefer the standard remote plan/apply flow over local-only flags.
  • Match workspace execution mode to how CI invokes Terraform.
  • Avoid -target in routine pipelines against remote workspaces.

Related guides

Tired of flaky CI? Latchkey auto-heals failed jobs and retries them for you. Start free →