Terminate Process node does not terminate timer

RE: Terminate Process node does not terminate timer

davel001150 — Tue, 02 Oct 2018 19:08:40 GMT

Going through Process Nodes I can verify based on completion times that the Timer started first, then Terminate Process node ran, then the timer finished. Then those things which follow the timer all took place, and the last entry is the regular end event about 35 seconds after the Terminate Process.

To my knowledge this is only happening on our production environment.

RE: Terminate Process node does not terminate timer

charlesm492 — Mon, 01 Oct 2018 20:26:24 GMT

I would also suggest taking a look at the process history to be sure. Seeing anything come after a terminate process node in the history seems like a very strange issue.

RE: Terminate Process node does not terminate timer

ajinkyab277 — Mon, 01 Oct 2018 19:49:38 GMT

Can you try to check the process history to identify the sequence of execution of nodes. if anything else is triggering the timer node or any part of the process you can see that in process history. also check terminate is the last entry in process history

RE: Terminate Process node does not terminate timer

Umesh Patel — Mon, 01 Oct 2018 17:51:44 GMT

Hi,

This looks like a weird issue. I think issue can be with terminate event instead of timer. Because you are saying,
1. Timer is active even after terminate event is reached
2. Sub-Processes behaving strangely when the parent process is terminated
Is it possible to check and re-configure the terminate event and re-publish process model?

If issue is already resolved, could you please let us know what actually issue was?
Thanks.

RE: Terminate Process node does not terminate timer

vishnuv — Sat, 29 Sep 2018 03:04:09 GMT

Hi,
Here are 2 trail & error methods which you can try:
1. Remove activity chaining into the terminate nodes at both levels if any. If your use cases demands for an activity chain see for other options below.
2. See if you can add an extra UI task say for example Review & Confirmation to hold for a while, so there will not be 2 nodes triggering at the same time when the sub process closes.
3. Have the timer route to an XOR after you set a flag before you terminate the process. If the flag is satisfied then go to a terminate/ end node, if not execute the normal exception flow.
Hope, this helps.

Thanks.