End execution listener called even on interrupted tasks?

Hey guys,

when I add an execution listener to a service task of event type “end”, my tests indicate that the execution listener is always called, even if the service task is interrupted by a boundary error event.

Is this the intended behavior? The docs are not that clear to me. I’d expect that interrupted tasks do not count as “properly ended”.

I am now adding the execution listener to the sequence flow behind the service task, but I’d prefer if I could set the execution listener to where it semantically belongs.

Thanks for clarification.

Kind regards,

Hi @Brutus5000,

Yes, it is the intended behavior.