Hey guys,
I’m having some trouble to set up an error boundary event onto a multi-instance activity/sub-process to catch any business errors which would happen while executing the activity/sub-process. Take the following workflow for example:
The token got to the error end event but was not catches by the interrupting error boundary event defined. Could this be a bug in the broker itself? Or am I missing something here?
It seems to work fine with an interrupting timer boundary event.
I’m using
- camunda/zeebe:0.23.1
- camunda/operate:0.23.0