# Execution Commands
Source: https://docs.chain.link/cre/reference/cli/execution
Last Updated: 2026-07-09

> For the complete documentation index, see [llms.txt](/llms.txt).

The `cre execution` commands query workflow execution history from the CRE platform. Use them to debug failures, review capability timelines, and pull log lines without opening the web UI.

> **NOTE: Authentication required**
>
> Running `cre execution` commands requires you to be logged in. Run `cre whoami` to verify your session, or `cre login` to authenticate. See [Logging in with the CLI](/cre/account/cli-login) for details.

> **NOTE: Global flags**
>
> All `cre` commands support [global flags](/cre/reference/cli#global-flags) like `--env`, `--target`, `--project-root`, and `--verbose`.

For a quick health check on the workflow configured in your project, see [`cre workflow get`](/cre/reference/cli/workflow#cre-workflow-get), which shows deployment health and the most recent execution.

## `cre execution list`

Lists recent workflow executions from the CRE platform.

**Usage:**

```bash
cre execution list [workflow-id-or-name] [flags]
```

**Arguments:**

- `[workflow-id-or-name]` — (Optional) On-chain workflow ID (64-char hex, visible in [`cre workflow list`](/cre/reference/cli/workflow#cre-workflow-list)) or workflow name. When omitted, executions across all workflows are returned.

**Flags:**

| Flag                | Description                                                                     |
| ------------------- | ------------------------------------------------------------------------------- |
| `--status <string>` | Filter by execution status: `TRIGGERED`, `IN_PROGRESS`, `SUCCESS`, or `FAILURE` |
| `--start <string>`  | Start of time range in ISO8601 format (e.g. `2026-01-01T00:00:00Z`)             |
| `--end <string>`    | End of time range in ISO8601 format (e.g. `2026-01-02T00:00:00Z`)               |
| `--limit <int>`     | Maximum number of executions to return (max 100, default 20)                    |
| `--output <string>` | Output format. Use `json` to print a JSON array to stdout for scripting         |
| `--json`            | Shorthand for `--output=json`                                                   |

**Examples:**

```bash
cre execution list
cre execution list my-workflow
cre execution list my-workflow --status FAILURE
cre execution list my-workflow --start 2026-01-01T00:00:00Z --end 2026-01-02T00:00:00Z
cre execution list my-workflow --limit 50 --output json
```

***

## `cre execution status`

Shows detailed status for a single workflow execution, including top-level errors when the run has failed.

**Usage:**

```bash
cre execution status <execution-uuid> [flags]
```

**Arguments:**

- `<execution-uuid>` — (Required) Execution UUID from `cre execution list` or the CRE UI

**Flags:**

| Flag                | Description                                       |
| ------------------- | ------------------------------------------------- |
| `--output <string>` | Output format. Use `json` to print JSON to stdout |
| `--json`            | Shorthand for `--output=json`                     |

**Examples:**

```bash
cre execution status 7f3d8a12-b1c2-4d3e-9f0a-1b2c3d4e5f6g
cre execution status 7f3d8a12-b1c2-4d3e-9f0a-1b2c3d4e5f6g --output json
```

***

## `cre execution events`

Shows the ordered capability event timeline for a workflow execution, including per-event status, method, duration, and errors.

**Usage:**

```bash
cre execution events <execution-uuid> [flags]
```

**Arguments:**

- `<execution-uuid>` — (Required) Execution UUID

**Flags:**

| Flag                    | Description                                               |
| ----------------------- | --------------------------------------------------------- |
| `--capability <string>` | Filter events to a specific capability ID                 |
| `--status <string>`     | Filter events by status (e.g. `FAILURE`)                  |
| `--output <string>`     | Output format. Use `json` to print a JSON array to stdout |
| `--json`                | Shorthand for `--output=json`                             |

**Examples:**

```bash
cre execution events 7f3d8a12-b1c2-4d3e-9f0a-1b2c3d4e5f6g
cre execution events 7f3d8a12-b1c2-4d3e-9f0a-1b2c3d4e5f6g --capability fetch-price
cre execution events 7f3d8a12-b1c2-4d3e-9f0a-1b2c3d4e5f6g --status FAILURE --output json
```

***

## `cre execution logs`

Shows log lines emitted during a workflow execution.

**Usage:**

```bash
cre execution logs <execution-uuid> [flags]
```

**Arguments:**

- `<execution-uuid>` — (Required) Execution UUID

**Flags:**

| Flag                | Description                                                        |
| ------------------- | ------------------------------------------------------------------ |
| `--node <string>`   | Filter logs to a specific node or capability ID (case-insensitive) |
| `--output <string>` | Output format. Use `json` to print a JSON array to stdout          |
| `--json`            | Shorthand for `--output=json`                                      |

**Examples:**

```bash
cre execution logs 7f3d8a12-b1c2-4d3e-9f0a-1b2c3d4e5f6g
cre execution logs 7f3d8a12-b1c2-4d3e-9f0a-1b2c3d4e5f6g --node ProcessData
cre execution logs 7f3d8a12-b1c2-4d3e-9f0a-1b2c3d4e5f6g --output json
```

## Learn more

- [Monitoring & Debugging Workflows](/cre/guides/operations/monitoring-workflows) — Web UI monitoring dashboard
- [`cre workflow get`](/cre/reference/cli/workflow#cre-workflow-get) — Deployment health and recent execution for the workflow in `workflow.yaml`