For the complete documentation index, see llms.txt. This page is also available as Markdown.

list_automation_runs

One automation's firing history.

The recent firing history for one automation — each firing's trigger source, outcome, and the produced run.

Request

GET /api/v1/ops/projects/{project}/automations/{automationId}/runs?limit=20
Parameter
In
Type
Required
Description

project

path

string

yes

The project's public id.

automationId

path

string

yes

The automation's public id.

limit

query

integer

no

Max firings to return (default 20, max 100).

curl -H "Authorization: Bearer $TESTVIBE_API_KEY" \
  "$TESTVIBE_SERVER/api/v1/ops/projects/$PROJECT/automations/$AUTOMATION/runs?limit=20"
testvibe automations runs $AUTOMATION

Tool list_automation_runs{ "automationId": "a1b2c3d4-…", "limit": 20 }.

Response

200 OK — an array of firings, newest first.

[
  {
    "id": "f0f0f0f0-0000-0000-0000-000000000000",
    "triggerSource": "schedule",
    "status": "dispatched",
    "runId": 318,
    "triggeredUtc": "2026-06-16T12:00:01.0000000Z",
    "detail": { "source": "schedule", "dispatch": { "action": "run_features", "runs": [ { "featureId": 12, "runId": 318 } ] } }
  }
]

triggerSource is schedule / event / manual; status is dispatched / skipped / error. runId links a dispatched firing to the run in the Runs view; detail carries the skip reason, error, or dispatch metadata.

Errors

HTTP
When

404 not_found

No such project, or no such automation in this workspace.

Last updated

Was this helpful?