Terminate Process node does not terminate timer

Certified Lead Developer

We have a process that has a timer going for 30 seconds in a branched flow.  If the primary branch completes first it hits a terminate node that's expected to cancel the timer midway through, and that's exactly what it does in every instance, unless it's on our production environment.

On our production environment only, we're seeing the terminate node fire, then the timer finish a little under 30 seconds later, script tasks after it also complete without any problems, and finally and end node not set to terminate.  Since that's the only other one in the process model, it completes the process again and we see two outbound flows in the parent process.

I see other issues with sub-processes behaving strangely when the parent process is terminated.  This is not what's happening.  The terminate node and the timer are on the SAME process model.  What in the world could keep the timer active after the process it's in has been terminated?

  Discussion posts and replies are publicly visible

Parents
  • 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.
Reply
  • 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.
Children
No Data