# List node executions

> operationId: `listRunNodes`


## Request

Lists node execution results. This call queries the current execution records; it is not an event stream. The nodeId, workflowRevisionId, invocationPath, executionId, and status parameters are optional single-value exact-match filters, and they are combined with AND. The executionId filter matches items[].id. Retries of the same invocation update the same id and attempts. A new invocation in a loop or child workflow gets a new id, so do not merge records by nodeId alone. Records are appended in a stable order of first publication. On each round, reread from page=1 and overwrite your local cache by id. Do not use nodeId, total, or the last page as an incremental watermark. Pages read while the run is active are not a consistent snapshot. After the run reaches a terminal state, read all pages without a status filter to reconcile. For details, see [Run observation and request recovery](/browser-rpa/api/observation). The data field returns the node's actual output as is, without redaction (credentials, cookies, values derived from private parameters, and local paths all appear in plaintext). Only ElementRef/FrameRef handles appear as `{kind,available:false}`, and they cannot be reused across runs. When present, matchedIndex starts at 1.

- **Prerequisites**: You have a run ID that you can read.
- **Authentication**: Same as the rest of the Local API; see [Authentication](/api-reference/getting-started/authentication). Resources belong to the current account/team data scope.
- **Side effects**: None. This call doesn't write business data.
- **Completion signal**: A 200 returns the execution record of each node invocation.
- **Retries**: Read-only calls can be retried. On 429 or 503, back off as indicated by Retry-After.


### Endpoint

```http
GET /api/rpa/browser/v1/runs/{runId}/nodes
```

Local API: `http://127.0.0.1:<port>/api/rpa/browser/v1/runs/{runId}/nodes`. Use the port configured in the client.

### Headers

| Parameter | Type | Required | Description and constraints |
|  --- | --- | --- | --- |
| `Authorization` | string | When Local API authentication is enabled | See [Authentication](/api-reference/getting-started/authentication). |


### Path parameters

| Parameter | Type | Required | Description and constraints |
|  --- | --- | --- | --- |
| `runId` | string | Yes | ID of the run. Min length 1; max length 128. |


### Query parameters

| Parameter | Type | Required | Description and constraints |
|  --- | --- | --- | --- |
| `page` | integer | No | Page number, starting at 1. Minimum 1; default 1. |
| `pageSize` | integer | No | Items per page. Default 20, maximum 100. Minimum 1; maximum 100; default 20. |
| `nodeId` | string | No | Stable node ID in the template. Min length 1; max length 128. |
| `workflowRevisionId` | string | No | Revision ID of the root or child workflow that the node belongs to. Min length 1; max length 128. |
| `invocationPath` | string | No | Opaque string copied from items[].invocationPath. It is matched exactly, and its structure is not parsed. Min length 1; max length 4096. |
| `executionId` | string | No | Matches items[].id, the record ID of one node invocation. It is not the nodeId. Min length 1; max length 128. |
| `status` | `running` / `success` / `failed` / `cancelled` | No | A single node execution status only, not a run status. Combined with the other filters using AND. |


### Request body

No request body.

### Request example

This is a documentation example; it was not sent to a live client. Set `RPA_BASE_URL` as described in [API conventions](/browser-rpa/api/common). Resource variables, the catalog revision, and ETags come from actual responses.

```bash
curl -i -X GET "${RPA_BASE_URL}/runs/${RPA_RUN_ID}/nodes?page=1&pageSize=20"
```

## Response

### 200

A 200 returns the execution record of each node invocation.

Body: `application/json`. The top-level `data` uses the model below. For `meta`, see [Metadata](/browser-rpa/api/data-types#metadata).

| Field | Type | Required | Description and constraints |
|  --- | --- | --- | --- |
| `items` | array<[NodeExecution](/browser-rpa/api/data-types#nodeexecution)> | Yes | Array of items on the current page or in the current resource. |
| `total` | integer | Yes | Total number of matches. Minimum 0. |
| `page` | integer | Yes | Page number, starting at 1. Minimum 1. |
| `pageSize` | integer | Yes | Items per page. Default 20, maximum 100. Minimum 1; maximum 100. |


### Response example

All IDs, timestamps, hashes, and run results are sample data. They don't indicate that the sample was executed.

```json
{
  "data": {
    "items": [
      {
        "dataTruncated": false,
        "id": "node_execution_example",
        "nodeId": "url_result",
        "workflowRevisionId": "revision_example_1",
        "invocationPath": "root",
        "status": "success",
        "attempts": 1,
        "startedAt": 1793318402000,
        "endedAt": 1793318402100,
        "durationMs": 100,
        "data": {
          "value": "https://example.com/",
          "url": "https://example.com/",
          "origin": "https://example.com",
          "pathname": "/",
          "query": {}
        },
        "error": null,
        "artifacts": []
      }
    ],
    "total": 1,
    "page": 1,
    "pageSize": 20
  },
  "meta": {
    "requestId": "7d498f20-7bab-4e59-9b05-88daf51230e9",
    "catalogRevision": "sha256:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa"
  }
}
```

### Error responses

| HTTP | error.code | What to do |
|  --- | --- | --- |
| 413 | RPA_LIMIT_EXCEEDED | details.limit=nodePageBytes. Reduce pageSize and rescan from page=1. If pageSize=1 still exceeds the limit, report the limit. |


For common 400/401/403/404/429/5xx errors and failure fields, see [Errors and recovery](/browser-rpa/api/common#errors-and-recovery). Error response example (403):

```json
{
  "error": {
    "code": "RPA_PERMISSION_DENIED",
    "message": "The request Host or Origin is not allowed, or the current identity can't access the target environment",
    "retryable": false,
    "issues": [],
    "details": null
  },
  "meta": {
    "requestId": "7d498f20-7bab-4e59-9b05-88daf51230e9",
    "catalogRevision": "sha256:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa"
  }
}
```

## Related

[Local API reference](/browser-rpa/local-api) · [API conventions](/browser-rpa/api/common) · [Data models](/browser-rpa/api/data-types) · [Workflow structure](/browser-rpa/api/workflow) · [Quickstart](/browser-rpa/quickstart)

### Timing semantics

`durationMs` is the action duration recorded by the executor. `startedAt` and `endedAt` are the times at which the service received the node states, so they include messaging and persistence overhead. Do not expect durationMs to equal endedAt−startedAt. In URL results, pathname is the web page path (such as `/fixture`). Local file paths are also returned as is.