Activate jobs
POST/jobs/activation
Iterate through all known partitions and activate jobs up to the requested maximum.
Request
- application/json
Body
required
the job type, as defined in the BPMN process (e.g. <zeebe:taskDefinition type="payment-service" />)
the name of the worker activating the jobs, mostly used for logging purposes
a job returned after this call will not be activated by another call until the timeout (in ms) has been reached
the maximum jobs to activate by this request
a list of variables to fetch as the job variables; if empty, all visible variables at the time of activation for the scope of the job will be returned
The request will be completed when at least one job is activated or after the requestTimeout (in ms). If the requestTimeout = 0, a default timeout is used. If the requestTimeout < 0, long polling is disabled and the request is completed immediately, even when no job is activated.
a list of IDs of tenants for which to activate jobs
Responses
- 200
- 400
- 500
The list of activated jobs.
- application/json
- Schema
- Example (from schema)
Schema
- Array [
- ]
jobs object[]
the key, a unique identifier for the job
the type of the job (should match what was requested)
the job's process instance key
the bpmn process ID of the job's process definition
the version of the job's process definition
the key of the job's process definition
the associated task element ID
the unique key identifying the associated task, unique within the scope of the process instance
customHeaders object
a set of custom headers defined during modelling; returned as a serialized JSON document
Additional properties allowed.
the name of the worker which activated this job
the amount of retries left to this job (should always be positive)
when the job can be activated again, sent as a UNIX epoch timestamp
variables object
All variables visible to the task scope, computed at activation time
Additional properties allowed.
The ID of the tenant that owns the job
{
"jobs": [
{
"jobKey": 0,
"type": "string",
"processInstanceKey": 0,
"processDefinitionId": "string",
"processDefinitionVersion": 0,
"processDefinitionKey": 0,
"elementId": "string",
"elementInstanceKey": 0,
"customHeaders": {},
"worker": "string",
"retries": 0,
"deadline": 0,
"variables": {},
"tenantId": "string"
}
]
}
The provided data is not valid.
- application/problem+json
- Schema
- Example (from schema)
Schema
Default value: about:blank
A URI identifying the problem type.
A summary of the problem type.
Possible values: >= 400
and <= 600
The HTTP status code for this problem.
An explanation of the problem in more detail.
A URI identifying the origin of the problem.
{
"type": "about:blank",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string"
}
An internal error occurred while processing the request.
- application/problem+json
- Schema
- Example (from schema)
Schema
Default value: about:blank
A URI identifying the problem type.
A summary of the problem type.
Possible values: >= 400
and <= 600
The HTTP status code for this problem.
An explanation of the problem in more detail.
A URI identifying the origin of the problem.
{
"type": "about:blank",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string"
}