AnsweredAssumed Answered

sending signal doesn't activate process

Question asked by ms1 on Mar 22, 2016
Latest reply on Mar 23, 2016 by ms1
Hello All,

I am working on a new process which will have a timer (the user specifies when an event will run) and also has the ability for the user to run the event now instead of waiting for the scheduled time. So, the user would schedule a time, decide to run it before then and the process should continue now.

I found what sounds like a perfect fit with the event-based gateway :
and I am doing this flow.

However, when I send the signal programmatically with RuntimeService.signalEventReceived(…), nothing happens. What I am expecting to happen is that the timer event is cancelled and the process continues. I tried this method with the specific execution ids and even with no execution id which should signal all processes waiting for this event.
I checked the db and see the entry in ACT_RU_EVENT_SUBSCR, so I know that it the process is running and waiting.

Does anyone have an idea why this isn't working?