Current behavior:

• When there is a call activity with a boundary error event and the called process instance throws that error, then the called process instance appears in the history as if it was deleted. That means, it's end activity id is not set and a delete reason is set.

Expected behavior:

• the sub process instance ends regularly, i.e. no delete reason is set and the end activity id is set

Failing test case:
org.camunda.bpm.engine.test.bpmn.event.error.BoundaryErrorEventTest.FAILING_testCatchErrorOnCallActivityShouldEndCalledProcessProperly()