> For the complete documentation index, see [llms.txt](https://docs.infraglide.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infraglide.com/deployments-and-execution-history/resource-tracking.md).

# Resource Tracking & Status Badges

## Resource Tracking & Status Badges

After Terraform runs, InfraGlide records which resources were created, updated, or destroyed so you can see progress in Executions and status icons on the canvas.

***

### What Gets Tracked

#### Per-deployment rows (`deployment_resources`)

One row per Terraform resource address for a deployment, including:

* `resourceAddress`, `resourceType`, `resourceName`
* `action` — `create` | `update` | `delete` | `no-op`
* `status` — e.g. `pending`, `creating`, `created`, `updating`, `failed`, `destroyed`, `no-op`
* timestamps and optional `errorMessage` ![alt text](/files/CJFg2j6AyiOXRbaYxANL)

#### Deployed Inventory & Tracking

Successful applies update your recorded infrastructure inventory used by Deployed Resources and Drift Detection. The Executions UI automatically refreshes resource statuses while a run is active so newly created or updated resources appear in real time.

Canvas nodes flip to a running-style icon when apply starts, then update their status badges as the run finishes.

![alt text](/files/H0rBH6oAu2BduBDF55Op)

***

### Canvas Status Badges

Cloud component nodes show iconography for deployment-related states such as:

* success / deployed\
  ![alt text](/files/b2jvblGoetlcUKmwPhx1)
* running\
  ![alt text](/files/H0rBH6oAu2BduBDF55Op)
* failed\
  ![alt text](/files/zUSL77SZrRhhrarpBVqR)
* destroying / destroyed

![alt text](/files/hnoTdgp4XDIHMiyiir5y)

* pending / draft\
  ![alt text](/files/z4g96YCJTKn8EtNX5OFs)

These are visual cues — open **Executions** for address-level detail and errors.

Pipeline-level badges (toolbar / My Pipelines) summarize overall status: Deployed, Deploying, Destroying, Failed, Destroyed, Partial, and similar labels.

pipeline status draft ![alt text](/files/BHg5zwcxqwVhme5MjVqo) pipeline status failed ![alt text](/files/SbQa0jdUmdHDxuJOG6qZ) pipeline status success ![alt text](/files/sRNe82FOYo3GHGR54qs1) pipeline status destroyed ![alt text](/files/kGxBTbfskaimX6S0QjZN) pipeline status pending ![alt text](/files/4L4xHqLHlnT01VNR7FM0)

### Force Replace & Taints

From the node overflow menu you can mark a resource for force-replace when address resolution works. Combined with the deployment replace API, this helps recreate a single bad resource without destroying the whole stack.

***

### Tips

* Prefer Executions resource tables over guessing from canvas icons alone.
* `partial_success` deployments are especially important to inspect resource-by-resource.
* Inventory on **Deployed Resources** can include unmanaged cloud assets; that hub is broader than a single deployment’s `deployment_resources` list.

***

### See also

* [Execution History & Live Logs](/deployments-and-execution-history/execution-history.md)
* [Plan, Deploy & Destroy Actions](/deployments-and-execution-history/execution-actions.md)
* [Cloud Inventory Discovery](/cloud-sync-and-drift-detection/inventory-discovery.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.infraglide.com/deployments-and-execution-history/resource-tracking.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.