AnsweredAssumed Answered

Signal Event stays active after being signaled until following activity is completed

Question asked by cnayak on Apr 18, 2016
Latest reply on Apr 19, 2016 by martin.grofcik
This behavior is seen when there are multiple outgoing transitions from a signal event ( to either multiple user tasks or a timer event and user task). When the signal event is successfully signaled, the workflow correctly transitions to the next activities in the execution but the signal event lingers in the ACT_RU_EVENT_SUBSCR table. Completing any of the activities that follow the signal event makes this entry go away. Is this behavior intended and expected  or is this is bug ?

Outcomes