> ## Documentation Index
> Fetch the complete documentation index at: https://docs.salesgraph.com/llms.txt
> Use this file to discover all available pages before exploring further.

# get_run_status

> Poll an async run started by gtm_audit or org_audit.

Polls the status of an asynchronous run. Use it after [`gtm_audit`](/tools/gtm-audit) or
[`org_audit`](/tools/org-audit). While the run is in progress it returns a short status line;
once the run is `completed` it returns the full markdown result.

<ParamField path="kind" type="string" required>
  The run type. One of:

  * `"gtm-audit"` — for a run started by [`gtm_audit`](/tools/gtm-audit)
  * `"audit"` — for a run started by [`org_audit`](/tools/org-audit)
</ParamField>

<ParamField path="id" type="string" required>
  The run id returned by the tool that started the run.
</ParamField>

**Type:** synchronous · **Returns:** a status line, or the full result markdown when complete

## Example call

```json theme={null}
{
  "name": "get_run_status",
  "arguments": { "kind": "gtm-audit", "id": "aud_123" }
}
```

## Returns

**In progress** — a status line:

```markdown theme={null}
# GTM audit status

- id: aud_123
- status: running
```

**Completed** — the full audit markdown (for a GTM audit, the audit slides; for an org audit,
the rendered report).

**Not found** — returns `not found` if the id doesn't exist or belongs to another organization.

<Warning>
  The `kind` must match how the run was started. Polling a `gtm-audit` id with `kind: "audit"`
  (or vice versa) returns `not found`.
</Warning>

## Polling guidance

Audits take from tens of seconds to several minutes. Poll on an interval (e.g. every 10–20s)
rather than in a tight loop, and stop once `status` is `completed` or `failed`. See
[Async runs](/reference/async-runs).