> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/infrastructure-as-code-management/platform/workspaces/workspace-statuses.md).

# Workspace Statuses

This document provides an overview of workspace statuses, offering a quick glance at the number of workspaces in each status. It helps streamline workflow management by enabling you to filter and identify workspaces based on their current status.

**Workspace Statuses:**

* **Active:** Active workspaces are those with an active state file, provisioned from your OpenTofu/Terraform code.
* **Inactive:** Inactive workspaces are currently not in use and do not have an active state file.
* **Provisioning:** Workspaces with a provision pipeline running against them.
* **Destroying:** Workspaces undergoing the teardown process with a `destroy` pipeline actively running.
* **Drifted:** Workspaces where the actual infrastructure has drifted from the expected configuration. Go to [Drift detection](/infrastructure-as-code-management/platform/iacm-pipelines/operations-overview.md) to understand how Harness detects drift, or go to the [IaCM Remediation Agent](/infrastructure-as-code-management/platform/workspaces/remediation-agent.md) to reconcile drift with a generated pull request.
* **Apply\_Needed:** An `apply` is required to bring the infrastructure in sync with the workspace configuration.
  * This status appears when changes are detected but not yet applied, such as OpenTofu/Terraform code updates, modified variables or files, or changes to the provisioner version.
  * It is typically set after a plan step shows pending changes or when configuration is edited directly, helping you identify workspaces that are currently out-of-date.
* **Rollback\_Applied:** The workspace state was rolled back to a previous version from the State tab. Run a plan to reconcile the rolled-back state with your live infrastructure. Go to [Roll back workspace state](/infrastructure-as-code-management/platform/workspaces/state-rollback.md) to restore a previous version.
* **Failed:** Workspaces where the last operation did not complete successfully, requiring attention.

{% embed url="<https://app.tango.us/app/embed/1b445b45-6085-4964-a8c4-ab5c883f0a98?skipCover=false&defaultListView=false&skipBranding=false&makeViewOnly=true&hideAuthorAndDetails=true>" %}
Harness IaCM Workspace Status'
{% endembed %}

{% hint style="info" %}
**ENHANCED USABILITY**

For enhanced usability, set [default pipelines](/infrastructure-as-code-management/platform/iacm-pipelines/default-pipelines.md) in your workspace configuration, so you can run [provision](/infrastructure-as-code-management/platform/workspaces/provision-workspace.md) and [destroy](/infrastructure-as-code-management/platform/workspaces/destroy-workspaces.md) pipelines directly against the workspace you are reviewing.
{% endhint %}