Escalations Get Propagated to Suspended Executions

Dear Flowable experts,

we have observed that boundary escalation events on call activities get triggered even if the process instance they belong to is suspended.
Is it an expected behavior?

Proposal from our side would be to throw an exception on escalation propagation if the relevant catching event belongs to a suspended process instance.

Here is a pull request with a test and a proposal for a solution. Please let me know if it’s an acceptable way to go.
In case you think some modifications are required to the PR, please feel free to just comment there - I’ll be happy to address the issues.

Thanks in advance!

Best regards,
Vasil Tsimashchuk

The PR has been merged. Thank you!