Start a run
Start from a webhook, from Portal, or from a catalog trigger.
A start snapshots the live IR. The run keeps that snapshot even if someone edits the designer afterward.
Ways to start
| Trigger | How |
|---|---|
| Webhook | HMAC accept binds eventType → catalog webhookBind and starts retryably |
| Manual | Portal Start on the workflow (POST /api/v1/ops/workflows/{id}/start) |
| Message | Kafka consume on a catalog with topic / consumerGroup |
| Schedule | Catalog cron ticks the same start |
Operators start. Admins can stop, restart from a hop on a linear arm (not mid-fork), start a new run, or rollback compensate hops where the catalog defines them.
Correlation
The correlation id is the workflow id. Copy it from Webhooks Events, from the Start response, or from Runs.
How it looks in Portal
Workflow detail → Start. Runs table shows the new row. If the graph listens immediately, Tasks also lists it.
If this fails
| Symptom | Cause |
|---|---|
| 403 | Developer role cannot start |
| Start pending on the webhook row | Runtime was down — Retry start |
| Restart from hop disabled | The run is on a fork arm; v1 restart is linear only |
Next: Runs