What a workflow is
Durable orchestration of hops, waits, forks, and exclusive branches.
A workflow is a catalog graph that Connect executes durably. Jobs remain Camel-only and cannot wait. Workflows can.
Open WorkflowsWhen you use it
Use a workflow when work must survive retries, wait for a person, or fan out on a fork (notify Matrix and wait for Review). Use a job when the path is fire-and-forget Camel.
Graph vocabulary
| Node | Does |
|---|---|
| call | Invoke a hop (Camel direct: route) |
| listen | Wait for Review / Send data / partner callback |
| wait | Timer only |
| switch | Exclusive branch from a listen decision |
| fork | AND-split; join when every arm is terminal |
| end | Outcome Completed or skipped |
Listen is labeled Review in the designer. Operator chrome never says Temporal.
Contact-lead
HMAC accept starts contact-lead. A fork runs Matrix notify in parallel with Review. Approve → create Plane issue. Reject or timeout → skip Plane; the run is still Completed. Duplicate (partnerId, externalId) never starts a second graph.
Live catalog vs this run
The listing shows Live catalog vX. A run diagnose shows Live catalog vX · this run snapshotted vY. In-flight runs keep the graph they started with. Saving the designer updates the next start only.
How it looks in Portal
Workflows lists catalog workflows with last status. Open one for instances, Start, and Builder. Open a run from Runs or the instance table.
If this fails
| Symptom | Cause |
|---|---|
| Start does nothing | You are not an operator |
| Graph does not match designer | You are looking at a run snapshotted before the save |
| Waiting with no Task | Listen source is partner, or assignee filter hides it |
Next: Designer · Start a run