Optionalcontext: JobStateFlatten activity-level context paths into store-ready key/values
Write the dimensional address into the state payload
Flatten job-level context paths into store-ready key/values
Build the list of child activities to transition to
Resolve expire and persistent policies from config
Bootstrap $self, $job refs and output.metadata.au timestamp
Extract the job status from the last transaction result
Did the semaphore reach its threshold? (from transaction results)
Persist the full activity + job state in a single store call
Optionaltxn: ProviderTransactionIncrement/decrement the job semaphore
Optionaltxn: ProviderTransaction
Invokes another graph (sub-flow) and optionally waits for its completion. The
awaitactivity enables compositional workflows where one graph triggers another by publishing to itssubscribestopic, creating a parent-child relationship between flows.YAML Configuration
The
topicin the await activity must match thesubscribestopic of the child graph. Both graphs are defined in the same app YAML:Fire-and-Forget Mode
When
awaitis explicitly set tofalse, the activity starts the child flow but does not wait for its completion. The parent flow immediately continues. The child'sjob_idis returned as the output.Execution Model
Await is a Category A (duplex) activity:
process): Maps input data and publishes aStreamDataType.AWAITmessage to the engine stream. The engine starts the child flow.processEvent, inherited): Receives the child flow's final output, maps output data, and transitions to adjacent activities.See
AwaitActivity for the TypeScript interface