We have one parent process which has couple of sub-process nodes and User Input

Mahesh Sanga over 9 years ago

We have one parent process which has couple of sub-process nodes and User Input Task nodes which are configured as QuickTasks in the parent process. Due to an action by end user when the parent process is terminated(we configured end even as Terminate), the child processes are not being terminated though the sub-process node in the parent process has been cancelled.

The sub process node has configuration to run the sub-process as Synchronously.

We are unable to reproduce this behavior.

This is happening in our Production.

Discussion posts and replies are publicly visible

0 Mahesh Sanga over 9 years ago

Could anyone tell if you faced this issue before?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 vikask146 over 9 years ago

Due to an action by end user when the parent process is terminated - Can you please elaborate this ? AFAIK - Once parent process is terminated then no matter sub-process in active or not, will eventually terminated.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Shyam Bommakanti
Certified Lead Developer
over 9 years ago

All synchronous subprocesses will terminate with end event terminate configuration on parent process.

What the depth of subprocesses you have?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Mahesh Sanga over 9 years ago

@Shyam the depth is 5.

@Vikask, Your understading is correct. "Once parent process is terminated then no matter sub-process in active or not, will eventually terminated." This is not happening in one of our process model that is what our problem is. I am going to create an Appian Support case to investigate this further.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 ajinkyab277
Certified Lead Developer
over 9 years ago

Just to add in this, this issue is occurring at particular place only and not for all process models. We have tested this with sample process models and it works well.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Tom Ryan
Appian Employee
over 9 years ago

Are you activity chaining into a terminate node on any of the levels? If so, this can cause an issue where subprocesses are not terminated, as you have described. You should not need to chain into terminate nodes, so removing the activity chaining should resolve the issue.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 ajinkyab277
Certified Lead Developer
over 9 years ago

Yeah that's correct we do have the chaining between quick task and terminate node in parent process and there is no need of that chaining. But I tried to replicate issue with sample process models my adding chaining but here it works fine (sub process getting terminated). One more thing to mention here is this issue is not happening every time , its random behaviour that we are observing with that specific process model.
I will give try by removing the chaining and observing environment over next week to check for this issue.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Shyam Bommakanti
Certified Lead Developer
over 9 years ago

Same issue: forum.appian.com/.../b-34255
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 ajinkyab277
Certified Lead Developer
over 9 years ago

Its working fine after removing the chaining between terminate node of parent process
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Mahesh Sanga over 9 years ago

@TomRyan, could you please let us know if there is a fix for this issue in the future release ? (or has it been resolved already in any of the latest releases of Appian? we are facing this issue on Appian 7.3)
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel