Unexpected Behavior with error event subprocess depending on whether started from timer boundary event

I have two process. In one case I call a subprocess (a call activity) as part of a regular flow and in another I do this from a timer boundary event. That’s the only difference!

Works as expected!

Does not!

The called activity always terminates with an error. In the first case the event subprocess is kicked off from the error start event.

But in the case of the process that uses the timer boundary event, it does not! The top level process just dies!

Is this the expected behavior? I’m using the 7.8 engine.

Breaking news!

This way of creating the work flow does work!