Skip to main content

Module policy

Module policy 

Expand description

The policy byte of a Start record (and the flags of a Child record, which become the child’s start policy). Recorded so replay and recovery apply the same rules.

Constants§

ATTACH
The policy every start between workflows uses: attach to a run that exists, so a resent start never creates a second run.
CLOSE_ABANDON
CLOSE_CANCEL
CLOSE_MASK
Bits 4–5: what happens to a child when its parent closes.
CLOSE_TERMINATE
DETACHED
Bit 6: the parent does not wait for the child’s result.
FINISHED_ALLOW
FINISHED_IF_FAILED
FINISHED_MASK
Bits 2–3: starting an ID whose last run finished within retention.
FINISHED_REFUSE
FINISHED_USE_EXISTING
OBJECT
Bit 7: on a Start, the run is a keyed object (its workflow ID is <type>/<key>, its handlers are updates and its input is a state snapshot); on a Child, the operation is a call to an object’s handler rather than a child start (its input is the encoded call).
RUNNING_FAIL
RUNNING_MASK
Bits 0–1: starting an ID that is already running.
RUNNING_TERMINATE
RUNNING_USE_EXISTING