OrchestrationWatchingEnvironment scoped
Queues
Durable per-instance work, with batching, order, retries, and dead letters.
Instances4Placed in the selected environment
Replica freshness9 / 129 of 12 copies current
Regions3Holding a copy of this environment
In flight2Runtime work running right now
What it guarantees
A send can join the transaction around it, so the work becomes visible only once the write commits. Handlers drain ordered messages in batches, and a message that exhausts its attempts moves to a dead-letter stream an operator can read.
- Send work transactionally from an action or a workflow step
- Tune the batch and the retry policy without giving up order
- Read and replay a dead letter once the handler is corrected
Configured resources
What this capability is holding up in the environment in scope right now.
| Resource | Kind | State | Configuration |
|---|---|---|---|
| mailDelivery | Queue | Active | Batches of 25, five attempts |
| searchIndex | Queue | Active | Batches of 100, transactional sends |
| webhookRetry | Queue | Watching | Two dead letters waiting on a replay |
Telemetry
Waiting146Across three active queues
Oldest12 secondsOn the mailDelivery queue
Dead letters2Held for an operator to read
Recent activity
- Batch acknowledgedCompleted, 1 minute agomailDelivery completed 25 messages in order.
- Message dead-letteredObserved, 6 minutes agowebhookRetry exhausted its fifth attempt.