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
Optionaloptions: ExtensionTypeOptionaloptions: ExtensionTypeBuild the list of child activities to transition to
Resolve expire and persistent policies from config
Bootstrap $self, $job refs and output.metadata.au timestamp
pending flows will not transition from the trigger to adjacent children until resumed
Optionaloptions: ExtensionTypeExtract 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: ProviderTransactionOptionaltransaction: ProviderTransaction
The entry point for every workflow graph. Each graph must have exactly one
triggeractivity, which executes when the graph'ssubscribestopic receives a message (viahotMesh.puborhotMesh.pubsub).The trigger initializes the job, sets its unique ID and key, binds the incoming payload as the trigger's output data, and transitions to adjacent activities defined in the
transitionssection.YAML Configuration
Key Behaviors
stats.idis provided, it resolves via@pipeexpressions against the input data. Otherwise a UUID is generated.DuplicateJobErroris thrown (unless it's a crash-recovery scenario).{ pending: <seconds> }, the trigger creates the job but does not transition to children until resumed.See
TriggerActivity for the TypeScript interface