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

# List latest test executions

> Current run per sub-test. Coming soon.

<Info icon="clock">
  **Coming soon.** This endpoint is not live yet. The contract below is the
  planned shape and may change. Calling it today returns `404`.
</Info>

```
GET /public/beta/{env_id}/latest-test-executions
```

Current status snapshot: one row per live sub-test, updated in place. There is
**no** incremental feed (`synced_since` / `deleted_since`) on this dataset —
re-pull the full list (or filter with `test_ids`) when you want a refresh.

Rows whose parent test is deleted are omitted. Cloud monitors are typically
1:1 with `test_id`; dbt tests may have multiple sub-tests.

The execution `id` on each row **changes** when a new run overwrites the row.
The stable key is `sub_test_unique_id`.

## Query parameters

Shared pagination: `cursor`, `limit` (default `500`, max `2000`). Filter arrays
are any-of within a param, AND across params, max `1000` values each.

| Parameter          | Notes                                                                                          |
| ------------------ | ---------------------------------------------------------------------------------------------- |
| `sub_test_ids`     | Filter by `sub_test_unique_id`.                                                                |
| `test_ids`         | Latest rows for these tests.                                                                   |
| `asset_ids`        | Latest rows whose parent test is on these assets.                                              |
| `test_types`       | Parent test `test_type`. Extensible.                                                           |
| `definition_types` | Parent test `definition_type`. Extensible.                                                     |
| `source_types`     | Parent test `source_type`. Extensible.                                                         |
| `statuses`         | As stored: `PASS`, `WARN`, `FAIL`, `ERROR`, `SKIPPED`, `NO_DATA`.                              |
| `order_by`         | `id` (default) or `synced_at`. Here `id` means **`sub_test_unique_id`**, not the execution id. |
| `direction`        | `asc` (default) or `desc`.                                                                     |

## Response

List envelope `{ items, next_cursor, has_more }`. Item shape is shared with
[test execution history](/api/reference/test-executions/list-test-executions).

```json theme={null}
{
  "items": [
    {
      "id": "exec_9f3c2a",
      "test_id": "elementary_cloud.freshness_anomalies.analytics.orders",
      "sub_test_unique_id": "elementary_cloud.freshness_anomalies.analytics.orders",
      "sub_type": "freshness_anomalies",
      "column_name": null,
      "status": "PASS",
      "failure_count": 0,
      "start_time": "2026-08-20T11:55:00Z",
      "duration_seconds": 12.4,
      "quality_dimension": "freshness",
      "result_reason": "NO_ANOMALY_DETECTED",
      "exception": null,
      "description": null,
      "synced_at": "2026-08-20T11:55:10Z"
    }
  ],
  "next_cursor": "eyJ...",
  "has_more": true
}
```

| Field                | Notes                                                                                                          |
| -------------------- | -------------------------------------------------------------------------------------------------------------- |
| `id`                 | This run's execution id. On latest rows it **changes** when a new run overwrites the row.                      |
| `sub_test_unique_id` | Stable per sub-test. Path key for get-one.                                                                     |
| `status`             | As stored: `PASS`, `WARN`, `FAIL`, `ERROR`, `SKIPPED`, `NO_DATA`.                                              |
| `failure_count`      | Cloud freshness/volume often `0` — the signal is `status`.                                                     |
| `quality_dimension`  | Nullable. Examples: `completeness`, `uniqueness`, `freshness`, `validity`, `accuracy`, `consistency`.          |
| `result_reason`      | Nullable. Examples: `ANOMALY_DETECTED`, `NO_ANOMALY_DETECTED`, `PERMISSIONS_ERROR`, `NOT_ENOUGH_DATA_SAMPLES`. |
| `description`        | Empty string in storage is returned as `null`. No `metrics` in this cut.                                       |

## Example

```bash theme={null}
curl -H "Authorization: Bearer $ELEMENTARY_TOKEN" \
  "$BASE/$ENV_ID/latest-test-executions?test_types=elementary_cloud&limit=500"
```