---
title: "Execution history for one automation rule"
method: GET
path: "/api/workspaces/{workspaceId}/automations/{ruleId}/runs"
tags: ["Automations"]
---

# Execution history for one automation rule

`GET /api/workspaces/{workspaceId}/automations/{ruleId}/runs`

## Request

- Base URL: `https://hiveship.app/api`
- URL: `https://hiveship.app/api/api/workspaces/{workspaceId}/automations/{ruleId}/runs`
- Auth: API key in cookie `hiveship_access`

Newest first. Answers "did this rule fire, and what happened" — before this, the only record of an execution was a server log line, so a rule that silently stopped matching was invisible. A `SKIPPED` status means the rule matched but the workspace plan no longer includes automations.

## Path parameters

- `workspaceId` string, required
- `ruleId` string, required

## Query parameters

- `limit` string

## Response `200`

Run history

- object
  - `success` boolean, required
  - `data` object[], required
    - `id` string, cuid, required
    - `ruleId` string, cuid, required
    - `issueId` string, cuid, nullable, required
    - `trigger` string, required
    - `status` 'SUCCESS' | 'PARTIAL' | 'FAILED' | 'SKIPPED', required
    - `depth` integer, required
    - `actions` object[], required
      - `type` string, required
      - `status` 'SUCCESS' | 'FAILED' | 'SKIPPED', required
      - `error` string
    - `error` string, nullable, required
    - `createdAt` string, date-time, required

## Other responses

- `404`: Rule not found in this workspace

---

[API](https://skmtc.dev/hiveship/apis/hiveship-api.md) · [All operations](https://skmtc.dev/hiveship/apis/hiveship-api/llms.txt) · [OpenAPI document](https://skmtc.dev/hiveship/apis/hiveship-api/revisions/73d3e26544e4?raw)