ContractsWatchingEnvironment scoped
External effects
A third-party call runs through an explicit boundary with idempotency and compensation.
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 third-party system cannot join a transaction here. The effect boundary records the call, keeps one idempotency key across every retry, and runs the compensation it was given when later work fails.
- Grant network access only through a named effect boundary
- Reuse one high-entropy idempotency key across retries and replays
- Compensate a completed third-party call after the transaction around it fails
Configured resources
What this capability is holding up in the environment in scope right now.
| Resource | Kind | State | Configuration |
|---|---|---|---|
| charge-card | External effect | Active | Idempotent charge with a refund compensation |
| send-receipt | External effect | Active | Mail delivery with a retry policy |
| partner-webhook | External effect | Watching | One raised retry window |
Telemetry
Effect rate38 per secondPayments, mail, and webhooks
Retry rate0.6%Mostly transient upstream failures
Compensations1Over the last day
Recent activity
- Webhook retry succeededCompleted, 4 minutes agoThe retry reused the original idempotency key.
- Charge compensatedObserved, 11 hours agoA downstream failure ran the configured refund.