The events expected by the resumable. These events are collected on each execution as long as the event parent id and the expected key matches. The expected key is the event.id of the produced event.
The domained events produced by the machine in the last session
The unique identifier of the event that originally initiated this entire orchestration workflow. This serves as the root identifier for tracking the complete execution chain from start to finish.
parentid
for completion events to create a direct lineage back to the workflow's originThis enables tracing the entire execution path and ensures completion events reference the original triggering event rather than just the immediate previous step.
Reference to the parent orchestration's subject when orchestrations are nested or chained. This enables hierarchical orchestration patterns where one orchestration can spawn sub-orchestrations. When the current orchestration completes, its completion event is routed back to this parent subject rather than staying within the current context.
parentSubject$$
field in initialization eventsThe state used by the resumable
Current execution status of the orchestration workflow
This field tracks the lifecycle state of the workflow instance to determine whether it can accept new events and continue processing or has reached its terminal state.
active: The workflow is running and can accept events for processing. It may be waiting for service responses, processing initialization events, or handling intermediate workflow steps. The orchestrator will continue to route events to active workflows.
done: The workflow has completed its execution lifecycle. This status
is set when the handler returns a complete
event, indicating the workflow
has finished successfully. Done workflows will not process additional events
and their state is preserved for audit/debugging purposes.
Unique identifier for the machine instance
The event consumed by the machine in the last session