A set of custom headers defined during modelling
The associated task element ID
The unique key identifying the associated task, unique within the scope of the process instance
Report a business error (i.e. non-technical) that occurs while processing a job. The error is handled in the process by an error catch event. If there is no error catch event with the specified errorCode then an incident will be raised instead.
Fail the job with an informative message as to the cause. Optionally, pass in a
value remaining retries. If no value is passed for retries then the current retry
count is decremented. Pass in 0for retries to raise an incident in Operate. Optionally,
specify a retry backoff period in milliseconds. Default is 0ms (immediate retry) if not
specified.
Fail the job with an informative message as to the cause. Optionally, pass in a
value remaining retries. If no value is passed for retries then the current retry
count is decremented. Pass in 0for retries to raise an incident in Operate. Optionally,
specify a retry backoff period in milliseconds. Default is 0ms (immediate retry) if not
specified.
The key, a unique identifier for the job
The version of the job process definition
The job's process instance key
The key of the job process definition
The job type, as defined in the BPMN process (e.g. <zeebe:taskDefinition type="payment-service" />)
All visible variables in the task scope, computed at activation time.
The name of the worker that activated this job
Cancel the workflow.
Complete the job with a success, optionally passing in a state update to merge with the process variables on the broker.
Mark this job as forwarded to another system for completion. No action is taken by the broker. This method releases worker capacity to handle another job.
Generated using TypeDoc
The bpmn process ID of the job process definition