Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error variables clarification #5171

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
+6 −6
Open

Error variables clarification #5171

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/components/modeler/bpmn/error-events/error-events.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,7 +31,7 @@ An error can be thrown within the process using an error **end event**.
Alternatively, you can inform Zeebe that a business error occurred using a **client command**. This throw error client
command can only be used while processing a job.

In addition to throwing the error, this also disables the job and stops it from being activated or completed by other job workers. Refer to the [gRPC command](/apis-tools/zeebe-api/gateway-service.md#throwerror-rpc) for details.
In addition to throwing the error, this also disables the job and stops it from being activated or completed by other job workers. Refer to the [gRPC command](/apis-tools/zeebe-api/gateway-service.md#throwerror-rpc) and [REST request](/apis-tools/camunda-api-rest/specifications/throw-job-error.api.mdx) for details.

## Catching the error

Expand Down Expand Up @@ -79,7 +79,7 @@ In general, we recommend talking about business reactions, which are modeled in

## Variable mappings

All error variables are merged into the error catch event. These variables can be merged into the process instance by defining an output mapping at the error catch event.
Variables can be passed along into the error catch event with the payload when the error is thrown from the client command. These variables can be merged into the process instance by defining an output mapping at the error catch event.

Visit the documentation regarding [variable mappings](../../../concepts/variables/#inputoutput-variable-mappings) for more information.

Expand Down
4 changes: 2 additions & 2 deletions versioned_docs/version-8.6/components/modeler/bpmn/error-events/error-events.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,7 +31,7 @@ An error can be thrown within the process using an error **end event**.
Alternatively, you can inform Zeebe that a business error occurred using a **client command**. This throw error client
command can only be used while processing a job.

In addition to throwing the error, this also disables the job and stops it from being activated or completed by other job workers. Refer to the [gRPC command](/apis-tools/zeebe-api/gateway-service.md#throwerror-rpc) for details.
In addition to throwing the error, this also disables the job and stops it from being activated or completed by other job workers. Refer to the [gRPC command](/apis-tools/zeebe-api/gateway-service.md#throwerror-rpc) and [REST request](/apis-tools/camunda-api-rest/specifications/report-error-for-job.api.mdx) for details.

## Catching the error

Expand Down Expand Up @@ -79,7 +79,7 @@ In general, we recommend talking about business reactions, which are modeled in

## Variable mappings

All error variables are merged into the error catch event. These variables can be merged into the process instance by defining an output mapping at the error catch event.
Variables can be passed along into the error catch event with the payload when the error is thrown from the client command. These variables can be merged into the process instance by defining an output mapping at the error catch event.

Visit the documentation regarding [variable mappings](../../../concepts/variables/#inputoutput-variable-mappings) for more information.

Expand Down
4 changes: 2 additions & 2 deletions versioned_docs/version-8.7/components/modeler/bpmn/error-events/error-events.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,7 +31,7 @@ An error can be thrown within the process using an error **end event**.
Alternatively, you can inform Zeebe that a business error occurred using a **client command**. This throw error client
command can only be used while processing a job.

In addition to throwing the error, this also disables the job and stops it from being activated or completed by other job workers. Refer to the [gRPC command](/apis-tools/zeebe-api/gateway-service.md#throwerror-rpc) for details.
In addition to throwing the error, this also disables the job and stops it from being activated or completed by other job workers. Refer to the [gRPC command](/apis-tools/zeebe-api/gateway-service.md#throwerror-rpc) and [REST request](/apis-tools/camunda-api-rest/specifications/report-error-for-job.api.mdx) for details.

## Catching the error

Expand Down Expand Up @@ -79,7 +79,7 @@ In general, we recommend talking about business reactions, which are modeled in

## Variable mappings

All error variables are merged into the error catch event. These variables can be merged into the process instance by defining an output mapping at the error catch event.
Variables can be passed along into the error catch event with the payload when the error is thrown from the client command. These variables can be merged into the process instance by defining an output mapping at the error catch event.

Visit the documentation regarding [variable mappings](../../../concepts/variables/#inputoutput-variable-mappings) for more information.

Expand Down
Loading