You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Zeebe ThrowError RPC supports passing variables (used as arbitrary metadata and available from the BPMN process instance) along with the error. This is available in the current Zeebe release 8.6 and earlier releases back to at least 8.3:
This is a proposal to add support for passing variables as optional data for the binding alongside the existing jobKey, errorCode and errorMessage. If provided, the value of variables will be sent to the ThrowError command of the Zeebe client.
The text was updated successfully, but these errors were encountered:
scott-brady
pushed a commit
to scott-brady/dapr-components-contrib
that referenced
this issue
Dec 25, 2024
The Zeebe
ThrowError
RPC supports passing variables (used as arbitrary metadata and available from the BPMN process instance) along with the error. This is available in the current Zeebe release 8.6 and earlier releases back to at least 8.3:Currently the Dapr Zeebe Command Binding (as of 1.14) does not accept
variables
:https://docs.dapr.io/reference/components-reference/supported-bindings/zeebe-command/#throw-error
This is a proposal to add support for passing
variables
as optional data for the binding alongside the existingjobKey
,errorCode
anderrorMessage
. If provided, the value ofvariables
will be sent to theThrowError
command of the Zeebe client.The text was updated successfully, but these errors were encountered: