Understand parallel agents
Read product-owned tasks and attempts without confusing them with disposable runtime processes.
Outcome
You can distinguish durable product delegation from a disposable attempt runtime and know when parallel execution is genuinely available.
Prerequisites
Understand plans, tasks, and attempts.
Steps
- Treat every task as PostgreSQL-owned durable intent.
- Treat every attempt as one immutable try with its own generation and event sequence.
- Use product-level messages, approvals, budgets, and cancellations rather than runtime-local state.
- When parallel DAG execution activates, inspect downstream typed inputs before trusting a join.
The current checkpoint has one fake attempt. Multiple concurrent agents, durable fork/join, worker restart, cancellation propagation, and concurrency enforcement remain gated by the Temporal slice.
Verify
No local runtime session or process record is the sole copy of user-visible work. A process death must be representable as a failed, retryable attempt before parallel execution is claimed.
Recover
When an attempt process disappears, inspect canonical events and provider state, mark the attempt terminal through the owning workflow, and retry as a new identity only after ambiguity is reconciled.