---
title: "Get task run"
method: GET
path: "/v2/task-runs/{run_id}"
tags: ["Tasks"]
---

# Get task run

`GET /v2/task-runs/{run_id}`

Returns a single task run. Use this to poll for status updates.

<Note>This endpoint is in beta, read more [here](https://arize.com/docs/ax/rest-reference#api-version-stages).</Note>

## Path parameters

- `run_id` string, required — A universally unique identifier (base64-encoded opaque string).

## Response `200`

Returns a single task run object

- TaskRun — A task run is an async job that executes the work defined on a task. Runs are created by triggering an existing task (`POST /v2/tasks/{task_id}/trigger`). For `RUN_EXPERIMENT` tasks, `experiment_id` is populated after the experiment is provisioned; poll `GET /v2/task-runs/{run_id}` until `status` reaches a terminal state.
  - `id` string, required — The unique identifier for the task run.
  - `task_id` string, required — The parent task identifier (base64).
  - `experiment_id` string, nullable — Created experiment identifier (base64). Present only for `RUN_EXPERIMENT` task runs; null for all other task types.
  - `status` 'PENDING' | 'RUNNING' | 'COMPLETED' | 'FAILED' | 'CANCELLED', required — Status of a task run. - PENDING - The run has been created but not yet started. - RUNNING - The run is currently in progress. - COMPLETED - The run finished successfully. - FAILED - The run encountered an error and stopped. - CANCELLED - The run was cancelled before completion.
  - `run_started_at` string, date-time, nullable, required — When the run started processing.
  - `run_finished_at` string, date-time, nullable, required — When the run finished processing.
  - `data_start_time` string, date-time, nullable, required — Start of the data window evaluated. Null for run_experiment runs.
  - `data_end_time` string, date-time, nullable, required — End of the data window evaluated. Null for run_experiment runs.
  - `num_successes` integer, required — Number of successfully evaluated items.
  - `num_errors` integer, required — Number of items that errored during evaluation.
  - `num_skipped` integer, required — Number of items that were skipped.
  - `created_at` string, date-time, required — When the run was created.
  - `created_by_user_id` string, nullable, required — The unique identifier for the user who triggered the run.
  - `failure_reason` string, nullable — Human-readable explanation of why the run failed or was cancelled; null for successful runs. For example, when all matching data already has evaluation labels from a previous run, the task cancels with zero successes, errors, and skipped items, and this field explains that the task must be re-triggered with `override_evaluations` enabled to re-evaluate it.

## Other responses

- `400` — Invalid request
- `401` — Authentication is required
- `404` — Not found
- `429` — Rate limit exceeded

---

[API](https://skmtc.net/arize-ai/apis/arize-rest-api.md) · [All operations](https://skmtc.net/arize-ai/apis/arize-rest-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/arize-ai/arize-rest-api/versions/1e87d8a4cf69/schema)