> For the complete documentation index, see [llms.txt](https://docs.terrakube.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.terrakube.io/2.34.0/run-terraform/workspaces/starting-a-run.md).

# Starting a Run

Open a workspace and click **New Run** to start a job without waiting on a git push or the API. This is the native equivalent of the [CLI-driven Workflow](/2.34.0/run-terraform/workspaces/cli-driven-workflow.md) and [API-driven Workflow](/2.34.0/run-terraform/workspaces/api-driven-workflow.md) run-creation paths, and works for any workspace regardless of workflow type.

| Field           | Description                                                                                                                              |
| --------------- | ---------------------------------------------------------------------------------------------------------------------------------------- |
| Choose job type | The [Templates](/2.34.0/set-up/organizations/templates.md) to run, e.g. `Plan`, `Plan and Apply`, or a `Destroy` variant (shown in red). |
| Branch Name     | The git branch to run against. Leave as-is for CLI-driven workspaces — Terrakube manages this value itself in that workflow.             |

### Additional planning options

Expand **Additional planning options** to scope the plan the same way `terraform plan -target=... -replace=...` would from the CLI:

| Field             | Description                                                         |
| ----------------- | ------------------------------------------------------------------- |
| Target resources  | Limits the plan to these resource addresses and their dependencies. |
| Replace resources | Forces replacement of these resource addresses on the next apply.   |

Both fields autocomplete against the workspace's actual state resources — start typing to search, or type a full address (e.g. `aws_instance.example` or `module.foo.aws_instance.bar`) and press Enter to add it as free text.

{% hint style="info" %}
Target and replace addresses only apply to the run you're creating — they aren't saved on the workspace and don't affect future runs, including ones triggered by a webhook or the scheduler.
{% endhint %}

### Approve or discard a run

When a template requires approval, the run stops at **Waiting approval** and appears on the workspace overview as the **Current run**. Users in the approval team can **Approve** or **Discard** it from the overview or from the run page. The confirmation restates what the plan will do ("3 to add, 1 to change, 0 to destroy") and calls out any resources that will be destroyed.

<figure><img src="https://1229094460-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTN6M529qVFnas8hChf2y%2Fuploads%2Fgit-blob-26a04ab4c2f1c7932bc1acd41af8607f6ac5d8a2%2Frun-approval-bar.png?alt=media" alt="A run waiting for approval, with its policy checks"><figcaption><p>A run waiting for approval, with its policy checks</p></figcaption></figure>

<figure><img src="https://1229094460-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTN6M529qVFnas8hChf2y%2Fuploads%2Fgit-blob-c16f488d9341d7cf683ff4000bfd90aa3fea731b%2Fworkspace-overview-current-run.png?alt=media" alt="The workspace overview shows the run that needs action"><figcaption><p>The workspace overview shows the run that needs action</p></figcaption></figure>

* Terrakube records who approved the run and when, and shows it next to the run creator in the run details and run history.
* A run with unresolved [policy](/2.34.0/govern/policy-enforcement-opa.md) violations cannot be approved; open the run to review them.
* If more runs are queued behind the current one, the overview says how many and links to the **Runs** tab.
* Approvals do not time out by default. Administrators can set `InactiveJobsWaitingApprovalTimeoutHours` on the API to cancel runs that wait too long.

### Run-specific variables

Runs started from CI can carry variables that apply to that run only; see [API-driven Workflow](/2.34.0/run-terraform/workspaces/api-driven-workflow.md#variables-for-one-run).


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.terrakube.io/2.34.0/run-terraform/workspaces/starting-a-run.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.