Run history and failures

Run Library retains the operational record for Terraform actions. Use it to understand status and evidence, not as a place to copy raw customer infrastructure into support notes.

Typical time

5–20 minutes

You need

Project access

Outcome

A diagnosed or retained run

Step 1: Filter Run Library

Use project, workspace, environment, type, status, date range, search, and cursor pagination. Summary cards show total, successful, failed, pending, and approval context for the selected project.

History 1 of 5 · Screenshot placeholder

Find the relevant Terraform run

Show project-scoped filters and a synthetic page of Run Library.

Future capture briefReplace workspace, actor, environment, run, approval, date, and status data tied to a real customer.

Step 2: Read status and timeline

Open View details and confirm created, started, current/terminal state, duration, actor, runner profile, and parent run.

Active states include QUEUED, STARTING, RUNNING, and CANCEL_REQUESTED. Terminal states include SUCCEEDED, FAILED, LAUNCH_FAILED, STALE_FAILED, TIMED_OUT, and canceled variants.

History 2 of 5 · Screenshot placeholder

Read run status and timeline

Show a synthetic failed run with safe timeline, stage, and user-facing summary.

Future capture briefHide run/parent IDs, actor, provider connection, entitlement snapshot, request details, and raw failure payloads.

Step 3: Inspect the relevant evidence

Depending on action, open:

• plan summary and resource filters;
• resource map and exact resource log filter;
• policy scan and OPA result;
• Review Request and guardrails;
• cost estimate;
• safe logs and step summaries; and
• safe JSON or downloadable safe logs where permitted.

Use the smallest evidence necessary for diagnosis. Never export Terraform state or sensitive plan data.

History 3 of 5 · Screenshot placeholder

Inspect safe run evidence

Show run-detail tabs, a synthetic resource map, and safe step summary.

Future capture briefReplace resource addresses, file paths, logs, actors, provider identities, evidence digests, and all infrastructure details.

Step 4: Recover safely

• Re-run repeats an allowed action with a new idempotent run.
• Cancel run requests cancellation for an active cancellable run.
• Fix source or workspace configuration first when the failure will repeat.
• Save a new revision and run a new plan when code changed.
• Recreate review and approval when plan evidence changed.

History 4 of 5 · Screenshot placeholder

Choose re-run or cancel

Show the row menu with View details, Re-run, and a state-appropriate Cancel run.

Future capture briefUse staged history. Hide run IDs, actors, workspace names, error details, and provider context.

Step 5: Archive or remove from normal history

Archive run removes the run from the active view according to allowed actions. Delete run removes it from normal Terraform run history after a confirmation.

Deleting a run does not delete Terraform state, cloud resources, audit records, or governed evidence. Specifically, the retained boundary covers:

• Terraform workspace files;
• Terraform state;
• cloud resources;
• audit records;
• provider connections;
• policy evidence; or
• cost evidence.

The action cannot be used to erase governed apply evidence.

History 5 of 5 · Screenshot placeholder

Review the non-destructive history confirmation

Show Delete Terraform run with the retained-evidence explanation.

Future capture briefUse a synthetic terminal run. Do not show customer names, actors, IDs, state, cloud resources, policy evidence, or costs.

Check your result

Record the run’s terminal status, safe error code or summary, corrected cause, and whether a new revision, plan, review, or apply was required. Preserve the authoritative audit and evidence chain.

Common blockers

Re-run is unavailable

The backend action state does not allow rerun for this run or caller. Create the appropriate new action from the latest saved revision.

Resource map is unavailable

The run type, status, mapping data, or retained artifact may not support it. Use the safe run summary and logs without inferring missing resource evidence.

Deleting a run did not delete infrastructure

That is intentional. History deletion is not a Terraform destroy operation and never removes state or cloud resources.

Raw logs contain sensitive material

Do not paste them into documentation or tickets. Use bounded safe summaries and follow the approved incident process.