Hi all, I'm having a tricky issue with a Terminate event at a par

Mike Schmitt

Certified Lead Developer

over 8 years ago

Hi all,

I'm having a tricky issue with a Terminate event at a parent process. Basically the set up is this: a parent process simultaneously launches a user task and a subprocess containing timers and stuff. If the user completes their task in a timely fashion, a Terminate node is hit, which is intended to also terminate the subprocess (which is called synchronously if it was a question). Instead we have a situation where the subprocess stays alive for some reason and continues to fire timer events long after the parent process was closed, which is confusing to users.

As an attempted remedy I added a byReference boolean that will signal the subprocess to end - the subprocess then hits a non-terminate end node. But now what's happening is the parent process chains to the Terminate node, and then the subprocess hits its end node too, causing 2 flows to exit to the higher process flow, which just makes a bigger mess. ...

Discussion posts and replies are publicly visible

Parents

0 Mike Schmitt
Certified Lead Developer
over 8 years ago

The weird part is, the subprocess contains not only a timer node (which would usually fire a few days after the terminate comes in, and always fires in the very early morning), but also a few rule listener nodes, etc. Any time I try to reproduce this issue in our Dev environment, either by naturally running through the parent process flow or by manually kicking off the Terminate node in the parent, the child process terminates correctly; but in Production I keep finding instances where the parent obviously hit the Terminate node but the child process was seemingly unaffected.
I'll look into screenshots - it may need to be stripped down a bit first though.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 Mike Schmitt
Certified Lead Developer
over 8 years ago

The weird part is, the subprocess contains not only a timer node (which would usually fire a few days after the terminate comes in, and always fires in the very early morning), but also a few rule listener nodes, etc. Any time I try to reproduce this issue in our Dev environment, either by naturally running through the parent process flow or by manually kicking off the Terminate node in the parent, the child process terminates correctly; but in Production I keep finding instances where the parent obviously hit the Terminate node but the child process was seemingly unaffected.
I'll look into screenshots - it may need to be stripped down a bit first though.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data