Cancels a running process instance
Errors: NOT_FOUND:
Completes a job with the given variables, which allows completing the associated service task.
Errors: NOT_FOUND:
FAILED_PRECONDITION:
Creates and starts an instance of the specified process. The process definition to use to create the instance can be specified either using its unique key (as returned by DeployProcess), or using the BPMN process ID and a version. Pass -1 as the version to use the latest deployed version. Note that only processes with none start events can be started through this command.
Errors: NOT_FOUND:
FAILED_PRECONDITION:
INVALID_ARGUMENT:
Behaves similarly to rpc CreateProcessInstance
, except that a successful response is received when the process completes successfully.
Deploys one or more processes to Zeebe. Note that this is an atomic call, i.e. either all processes are deployed, or none of them are.
Errors: INVALID_ARGUMENT:
Deploys one or more resources (e.g. processes or decision models) to Zeebe. Note that this is an atomic call, i.e. either all resources are deployed, or none of them are.
Errors: INVALID_ARGUMENT:
Marks the job as failed; if the retries argument is positive, then the job will be immediately activatable again, and a worker could try again to process it. If it is zero or negative however, an incident will be raised, tagged with the given errorMessage, and the job will not be activatable until the incident is resolved.
Errors: NOT_FOUND:
FAILED_PRECONDITION:
Modifies the process instance. This is done by activating and/or terminating specific elements of the instance.
Errors: NOT_FOUND:
FAILED_PRECONDITION:
INVALID_ARGUMENT:
Publishes a single message. Messages are published to specific partitions computed from their correlation keys.
Errors: ALREADY_EXISTS:
Resolves a given incident. This simply marks the incident as resolved; most likely a call to UpdateJobRetries or SetVariables will be necessary to actually resolve the problem, following by this call.
Errors: NOT_FOUND:
Updates all the variables of a particular scope (e.g. process instance, flow element instance) from the given JSON document.
Errors: NOT_FOUND:
Reports 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.
Errors: NOT_FOUND:
FAILED_PRECONDITION:
Obtains the current topology of the cluster the gateway is part of.
Updates the number of retries a job has left. This is mostly useful for jobs that have run out of retries, should the underlying problem be solved.
Errors: NOT_FOUND:
INVALID_ARGUMENT:
Generated using TypeDoc
Iterates through all known partitions round-robin and activates up to the requested maximum and streams them back to the client as they are activated.
Errors: INVALID_ARGUMENT: