OrchestrationOperationalEnvironment scoped
Schedules
Intervals, cron rules, and one-shot calls invoke a contract per instance.
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 schedule belongs to the module that owns the contract it calls. Its overlap policy decides whether a late invocation is skipped, queued, or run alongside the next boundary.
- Declare an interval or a cron schedule as an exported value
- Choose whether a late run is skipped, queued, or runs alongside
- Register a one-shot call on one instance for a precise future time
Configured resources
What this capability is holding up in the environment in scope right now.
| Resource | Kind | State | Configuration |
|---|---|---|---|
| flushPresence | Interval | Active | Every 60 seconds, skips an overlap |
| expireHolds | Cron | Active | Every 15 minutes, queues an overlap |
| releaseReservation | One-shot | Ready | Two instance calls pending |
Telemetry
Configured7Five recurring and two one-shot
Next call43 secondsflushPresence
Late starts0Over the last day
Recent activity
- flushPresence completedCompleted, 1 minute ago41 subscriber leases checked for battles/room-42.
- One-shot call registeredValidated, 5 minutes agowallet/player-9001 releases its hold at the deadline.