https://api.planasonix.comAuth:
Authorization: Bearer plus your API key or JWT.
GET /api/runs
List runs across pipelines with filters.
Only runs for this pipeline.
queued, running, succeeded, failed, canceled, and so on.Encoded range (for example
2025-03-01..2025-03-31) or separate from/to if your deployment exposes them.Page size.
Pagination cursor.
GET /api/runs/{id}
Full run record: status, timing, row counts, errors, and trigger metadata.
Run ID.
Terminal or in-progress state.
Aggregated counters (rows read/written, bytes, cost units).
Present when
status is failed; includes message and optional stack reference.GET /api/runs/{id}/nodes
Per-node execution: start/finish times, state, retries, and row counts.
Run ID.
GET /api/runs/{id}/logs
Execution logs (plain text chunks, JSON lines, or URLs to object storage, depending on deployment).
Run ID.
Filter to a single node’s log stream.
ISO timestamp or log cursor for incremental fetch.
DELETE /api/runs/{id}
Request cancellation of a running or queued run. Completed runs return 409 or 400 depending on policy.
Run ID.
Status reference
| Status | Meaning |
|---|---|
queued | Scheduled or manual run waiting for capacity |
running | Actively executing |
succeeded | All nodes completed without fatal errors |
failed | One or more nodes failed or policy aborted the run |
canceled | User or system canceled the run |
Related
Trigger a run
POST /api/pipelines/{id}/runRun history (UI)
How runs appear in the product.