Runs

Runs record execution of a saved pipeline snapshot, including the selected version, trigger and actor. A pipeline ID identifies the reusable graph; a run ID identifies one execution.

GET /projects/{projectId}/runs requires runs:read and an administrator-linked actor. It accepts limit, offset, status and pipelineId, returning {runs, pagination}. GET /projects/{projectId}/runs/{runId} returns run details after checking the run's pipeline belongs to the selected project.

curl --fail-with-body --get -H "Authorization: Bearer $SEMOGRAM_API_KEY" \
  --data-urlencode "pipelineId=$SEMOGRAM_PIPELINE_ID" \
  --data-urlencode 'limit=10' \
  "https://platform.semogram.com/api/v1/projects/$SEMOGRAM_PROJECT_ID/runs"

The variables are the secret workspace key and actual project/pipeline UUIDs. Inspect the returned run, then request its detail with the returned run ID. A running or queued run is not a failed HTTP request; poll that run rather than starting another execution.

Resolve an unsuccessful run

Check step results, error evidence, endpoint capability access and the recorded version. Verify whether the destination changed before repeating a write. The run snapshot preserves what was submitted; editing the current draft does not repair a historical run.

No public HTTP run cancellation, resume or schedule route exists. Use pipeline recovery for the supported platform flow. A query result job's DELETE action applies to query jobs, not pipeline runs.