Escalation intermediate throw event

BPMN & Modeling Discussion & Questions
1

Hi, I am new to BPMN and Camunda and just started using it.

I see that there is an escalation intermediate throw event which can be used for subprocess to inform something to the parent process. As per my understanding, the subprocess flow will not be interrupted and in parent process if there is escalation boundary event non-interrupting then it will catch the subprocess event and continue to required steps while not affecting the original parent process flow.

I want to know why is this element called as escalation intermediate throw event and not escalation intermediate throw event(non-interrupting) in that case?

2

It because the throw event itself has no impact on if the process will be interrupted or not.
It’s the catching event that will actually interrupt the process. Which is why there’s only one throw event but an interrupting catch and non-interrupting catch.

2 Likes