---
title: "Get execution status (lightweight, no steps)"
method: GET
path: "/executions/{id}:getStatus"
tags: ["Executions"]
---

# Get execution status (lightweight, no steps)

`GET /executions/{id}:getStatus`

## Response `200`

Status summary.

- ExecutionStatusSummary — Lightweight execution status (no steps payload).
  - `id` string, required — ULID identifier (26-char Crockford base32).
  - `workflowId` string — ULID identifier (26-char Crockford base32).
  - `status` 'pending' | 'waiting' | 'success' | 'failed' | 'error', required — Outcome of an execution. `pending` is in-flight; `waiting` is suspended mid-workflow at an `await` node, durably parked until a signal arrives (a human approve/reject or an operator-observed chain event) or the wait times out — non-terminal, like `pending`, but distinguishable so a client can show "awaiting approval"; `success` is full success; `failed` is logical failure (e.g., a node returned an error, or a wait timed out); `error` is a system / infrastructure failure (e.g., RPC unreachable).
  - `startAt` integer
  - `endAt` integer
  - `error` string

## Other responses

- `401` — Missing or invalid bearer token.
- `404` — Resource not found.

---

[API](https://skmtc.net/avaprotocol/apis/ava-protocol-avs-api.md) · [All operations](https://skmtc.net/avaprotocol/apis/ava-protocol-avs-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/avaprotocol/ava-protocol-avs-api/versions/231d563f2c9f/schema)