> 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/execution-history.md).

# Execution History & Live Logs

## Execution History & Live Logs

### Every Preview, Deploy, and Destroy creates a **deployment** record you can inspect later. During a run you can stream logs live; afterward you can reload historical output from Loki or stored logs. ![alt text](/files/9fEi4zhxh1nYsPfELc1D)

### Where to Find History

| Surface                       | Content                                                             |
| ----------------------------- | ------------------------------------------------------------------- |
| Designer → **Executions** tab | Per-pipeline history, live/historical logs, plan summary, resources |

![alt text](/files/AUYZrHkBT8zjwL4UWFtW) | **My Pipelines** | Deployment status column / chips (not full log viewer) |

![alt text](/files/ewmhSxk2MzcFTBCxcV7G) | **Observability → Deployment Logs** | Cross-pipeline historical log browser |

![alt text](/files/WxkdBxxdUq0LBeD1eP0T)

Save the pipeline before Executions can load history.

***

### Status Lifecycle

Common statuses:

| Status    | Meaning                         |
| --------- | ------------------------------- |
| `pending` | Record created, not yet running |

![alt text](/files/T0NRCJFgOHVrbDH6dQuJ) | `in progress` | Execution in progress ||

![alt text](/files/m5tVk6qVcWc3sP0lo5s3) | `planned` | `plan` finished successfully |

![alt text](/files/6PDfwR8eK0gZJNYHidSl) | `success` | `apply` finished successfully |

![alt text](/files/t9kxHM789xldmiB3SoGY) | `partial_Deployed` | Apply created some resources then errored |

![alt text](/files/kmO9fhkVoFHjktORj7qB) | `failed` | Execution failed |

![alt text](/files/n6KanMbOQP2mZIj8H09S) | `destroyed` | Destroy finished successfully |

![alt text](/files/1P7112RzzEDaKUMlSIAc)

UI-only labels such as **Destroying** / **Deploying** may be derived while `running`. Startup recovery marks stuck `pending`/`running` rows as failed after a server restart. Stale cleanup can fail long-running pending/running rows after time thresholds.

***

### Live Logs (WebSocket)

While a deployment is active, InfraGlide streams real-time execution logs directly to your browser console overlay. You can watch step-by-step Terraform output line by line as resources are provisioned or destroyed.

***

### Historical Logs & Log Retention

Once a deployment finishes:

* Log history remains accessible under the **Executions** tab for historical review.
* Both the designer console overlay and the **Executions** tab share the same real-time and historical log views.
* Log text automatically redacts sensitive cloud provider credentials or tokens to keep your team compliant.

***

### What Is Stored on the Deployment

* `terraformOutput` — redacted full output
* `deploymentLogs` — redacted log text (when written)
* `planSummary` — parsed plan JSON summary for plan runs
* `createdResources` — snapshot of addresses after apply/destroy
* `tfAction` — `plan` | `apply` | `destroy`

Ask Jane from the log view for failure analysis (see [Deployment Error Analysis](/jane-ai-copilot/error-analysis.md)).

***

### Polling Behavior

The designer polls status about every **3 seconds**, with a long overall timeout (tens of minutes) matching Terraform run duration. Terminal statuses stop the wait loop: `failed`, `success`, `planned`, `destroyed`, `partial_success`.

***

### See also

* [Plan, Deploy & Destroy Actions](/deployments-and-execution-history/execution-actions.md)
* [Resource Tracking & Status Badges](/deployments-and-execution-history/resource-tracking.md)
* [Deployment Error Analysis](/jane-ai-copilot/error-analysis.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/execution-history.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.