js-bao-wss-client / WorkflowStatusSlice
Interface: WorkflowStatusSlice
A slice record the client can vouch for. Field for field with the Swift client's WorkflowSliceInfo.
Timestamps are epoch milliseconds (what the route sends), not the ISO-8601 strings a run record carries — the slice record is the platform's own bookkeeping, and the client passes its numbers through verbatim.
Properties
ceilingAt
ceilingAt:
number|null
The 12-hour bound THIS slice ends at, epoch ms — startedAt plus the slice maximum, not a deadline for the run, which can continue in a later slice with a ceiling of its own.
lastRefreshAt
lastRefreshAt:
number|null
When the credential was last refreshed, epoch ms.
lastResetAt
lastResetAt:
number|null
When the most recent reset was counted, epoch ms; null until there is one.
lastResetCause
lastResetCause:
string|null
What named the most recent reset: "code-updated" when the platform build changed underneath the run, "evicted" when the runtime said it had reclaimed the run's memory, "unknown" when the platform saw the run interrupted but could not attribute it. null until there has been one. A plain string, for the same reason settledStatus is one.
refreshCount
refreshCount:
number
How many times the credential was refreshed through the gateway instead of yielding. 0 for a run short enough never to need one.
resets
resets:
number
How many of this run's slices the platform tore down and started again — a platform deploy interrupts every slice that is executing, and so does the runtime reclaiming memory.
The interrupted step is then run again as a further attempt, so a run that was reset and then finished reads completed with no failure and no error code: this count is the only place that history shows. 0 for a run nothing reset, and for a server that predates the field.
settledAt
settledAt:
number|null
When THIS slice settled, epoch ms; null while the slice is open. A settled slice is not a finished run: a slice that yielded settles here and the run continues in the next slice, so a caller watching a run still reads status, never this field.
settledStatus
settledStatus:
string|null
How THIS slice settled ("completed", "failed", "cpu-yield", …); null while the slice is open. "cpu-yield" is the slice that gave up its CPU budget for the run to carry on in another one.
sliceId
sliceId:
string
Id of the slice record. The one field the server always fills.
startedAt
startedAt:
number|null
When this slice started, epoch ms.