When specifying a camunda:errorMessage for a bpmn:error definition, the errorMessage is ignored when throwing a related BPMN error via the external task REST API.

Expected:
When I don't pass an error message with the REST call, I would expect that the errorMessage from the error definition is used as documented.

Root Cause:
The error message of the error definition is parsed, but ignored when handling the error instantiation and propagation.