Catch all error events by using empty 'errorCode' does not work

[ralfpuchert]

Describe the bug
Using an error catch event (boundary or start event in Subprocess) with an empty errorCode results in incident with errorType=UNHANDLED_ERROR_EVENT.
Also only error events with a non-empty errorCode will be reported like this: Available error events are [boundary].

To Reproduce

1. Create a BPMN process with error catch event as boundary event or as start event in subprocess.
2. Deploy, start the process. In a job client throw an error command with an unhandled errorCode.
3. Zeebe creates an incident instead of catching the error

Here an example process errorProcessCatchAll.bpmn.txt

Slack thread

Expected behavior

The error is caught and no incident is created.

Log/Stacktrace

Example error message from Zeebe:

errorType=UNHANDLED_ERROR_EVENT, errorMessage='Expected to throw an error event with the code 'unknown' with message 'Process error', but it was not caught. Available error events are [boundary]

Environment:

• OS: MacOS
• Zeebe Version: 8.2.0-alpha3 and later
• Configuration: ElasticsearchExporter

[lzgabel]

Hi @korthout. I think I found the problem, please assign this task to me, I will submit a PR to fix this problem soon. Thanks ❤️

[lzgabel]

BTW. As a workaround, user can catch all error events by removing the errorEventDefinition.