can the workflow be retried if an error occurs
the HotMesh connection configuration (io/redis NPM package reference and login credentials)
the reentrant semaphore, incremented in real-time as idempotent statements are re-traversed upon reentry. Indicates the current semaphore count.
number as string for the replay cursor
Optional
expire?: numberif present, the workflow will delay expiration for the specified number of seconds
holds list of interruption payloads; if list is longer than 1 when the error is thrown, a collator
subflow will be used
the HotMesh App namespace
entry point ancestor flow; might be the parent; will never be self
the native HotMesh message that encapsulates the arguments, metadata, and raw data for the workflow
the replay hash of name/value pairs representing prior executions
the dimensional isolation for the reentrant hook, expressed in the format 0,0
, 0,1
, etc
the workflow/job ID
the open telemetry span context for the workflow, used for logging and tracing. If a sink is enabled, this will be sent to the sink.
a concatenation of the task queue and workflow name (e.g., ${taskQueueName}-${workflowName}
)
the open telemetry trace context for the workflow, used for logging and tracing. If a sink is enabled, this will be sent to the sink.
the reentrant semaphore parent counter object for object reference during increment