# Why is PROCESS\_CANCELLED event sent from a terminate end event instead of PROCESS\_COMPLETED?

**URL:** <https://forum.flowable.org/t/why-is-process-cancelled-event-sent-from-a-terminate-end-event-instead-of-process-completed/87>\
**Category:** Flowable Engine\
**Created:** [November 8, 2016, 7:52pm UTC](https://forum.flowable.org/t/why-is-process-cancelled-event-sent-from-a-terminate-end-event-instead-of-process-completed/87 "2016-11-08T19:52:00Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![robert.hafner](https://avatars.discourse-cdn.com/v4/letter/r/e480ec/32.png) [@robert.hafner](https://forum.flowable.org/u/robert.hafner)\
**Post date:** [November 8, 2016, 7:52pm UTC](https://forum.flowable.org/t/why-is-process-cancelled-event-sent-from-a-terminate-end-event-instead-of-process-completed/87/1 "2016-11-08T19:52:00Z")

</div>

I noticed recently that the TerminateEndEventActivityBehavior sends a PROCESS\_CANCELLED event instead of a PROCESS\_COMPLETED event. Can you share the reason behind why PROCESS\_CANCELLED was chosen over PROCESS\_COMPLETED? We have been thinking about this a bit since it impacts our event-driven service and feel PROCESS\_COMPLETED might make more sense since the process designer modeled that the process should end when reaching this end event. Before deciding whether we should alter the behavior of flowable in our use case, we would first like to better understand the reason PROCESS\_CANCELLED was chosen from your perspective. Any insight on this decision would be extremely helpful to us. Thanks!

---

<div class="post-metadata">

**Author:** ![tijs](https://avatars.discourse-cdn.com/v4/letter/t/bc79bd/32.png) [@tijs](https://forum.flowable.org/u/tijs)\
**Post date:** [November 9, 2016, 7:10am UTC](https://forum.flowable.org/t/why-is-process-cancelled-event-sent-from-a-terminate-end-event-instead-of-process-completed/87/2 "2016-11-09T07:10:45Z")

</div>

Hi Rob,

I agree that a PROCESS\_COMPLETED event would make more sense. But it would be even better to introduce a new event type PROCESS\_COMPLETED\_WITH\_TERMINATE\_END\_EVENT I think. We also have this for the error end event. What do you think?

Thanks,

Tijs

---

<div class="post-metadata">

**Author:** ![robert.hafner](https://avatars.discourse-cdn.com/v4/letter/r/e480ec/32.png) [@robert.hafner](https://forum.flowable.org/u/robert.hafner)\
**Post date:** [November 9, 2016, 1:25pm UTC](https://forum.flowable.org/t/why-is-process-cancelled-event-sent-from-a-terminate-end-event-instead-of-process-completed/87/3 "2016-11-09T13:25:00Z")

</div>

I think defining a separate event type makes sense since it allows a listener to identify how the process was completed. I’ll create a PR for this change.

Thanks,  
Rob
