ScheduleFiringView

One schedule firing as a surface may consume it. The schedule ledger mints a planned RunId for every claim, including skips, but only a fired claim denotes a Run. Skipped planned ids therefore never cross this boundary.

Type object

Shape

Field	Type	Description
occurrence_msrequired	integer (int64)
revisionrequired	integer (uint32, >= 0)
outcomerequired	ScheduleFiringOutcome	The immutable outcome of one schedule occurrence.
run	RunId or null
busy_holder	RunId or null
atrequired	integer (int64)

Example

{
  "occurrence_ms": 0,
  "revision": 0,
  "outcome": "fired",
  "run": "00000000-0000-4000-8000-000000000000",
  "busy_holder": "00000000-0000-4000-8000-000000000000",
  "at": 0
}

The contract has no example values, so example bodies are generated from each schema: every field is shown with a placeholder of its type.

Generated from contract version 1. Last updated November 12, 2026.