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
Dispatches work to a registered callback function. The
workeractivity publishes a message to its configuredtopicstream, where a worker process picks it up, executes the callback, and returns a response that the engine captures as the activity's output.YAML Configuration
Worker Registration (JavaScript)
Workers are registered at initialization time via the
workersarray inHotMesh.init. Each worker binds atopicto acallbackfunction.Retry Policy
Retry behavior is configured at the worker level (not in YAML) via the
retryoption. Failed callbacks are retried with exponential backoff untilmaximumAttemptsis exhausted. ThemaximumIntervalcaps the delay between retries.Execution Model
Worker is a Category A (duplex) activity:
process): Maps input data and publishes a message to the worker's topic stream.processEvent, inherited): Receives the worker's response, maps output data, and executes the step protocol to transition to adjacent activities.See
WorkerActivity for the TypeScript interface