ContractsOperationalEnvironment scoped
Events
Typed committed messages fan out to subscribed callers and to instance consumers.
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
An event is an exported value with a validated payload. One emitted inside an action is published only after that transaction commits, so a subscriber never sees work that was rolled back.
- Declare a typed payload beside the module that owns it
- Publish only after the surrounding transaction commits
- Read which callers are subscribed from the instance itself
Configured resources
What this capability is holding up in the environment in scope right now.
| Resource | Kind | State | Configuration |
|---|---|---|---|
| settled | Event | Active | battles, emitted after the round commits |
| holdChanged | Event | Active | wallet, caller and workflow consumers |
| stockAdjusted | Event | Watching | inventory, regional subscribers |
Telemetry
Delivery rate3,400 per secondCommitted deliveries
Subscribers2,607In the selected environment
Delivery lag18 msp95 from commit to caller
Recent activity
- settled deliveredCompleted, 1 minute ago38 room subscribers received the committed payload.
- Subscriber count readObserved, 2 minutes agobattles/room-42 currently has 41 callers subscribed.