Appian Community and Appian Academy are being upgraded. From July 24–August 3, the Appian Community will be in read-only mode. During this time, the site will be read-only and user registration will be disabled. We apologize for any inconvenience this may cause, but a more secure, stable, and performant Community experience is coming soon!
The new Appian Community launches August 3, followed by Appian Academy on August 7. During the migration, Appian Community Edition, Appian Academy, Documentation, Certifications, Instructor-led Customer Training, Partner Sales Training & Accreditation, and Forum (for Appian Partners and Customers only) will remain available.
Hello team,
I have a parent process model from which I am triggering child process instances asynchronously using MNI.
The child process instances have been successfully triggered and have reached the end node. However, the parent process instance is still showing as Active in the Monitor tab since yesterday. Additionally, when I view the process instance and hover over each node, the Start Process node appears disabled, whereas the End Event node appears enabled. Could you please help me understand why the parent process instance is still in an active state despite the process reaching the end node?
As I am triggering child instances through MNI, my understanding is that if I use a Terminate End Event in the parent process, it will also terminate the child process instances. Therefore, I do not think that approach will work for my scenario. Please correct me if my understanding is incorrect.
Discussion posts and replies are publicly visible
Avoid relying on a Terminate End Event to guarantee your MNI async child subprocesses get cancelled. It should cancel them by default, but KB-1300 documents a known issue where activity chaining into the Terminate End Event causes it to run under the completing user's privileges, so cancellation silently fails if that user isn't a process admin.If the parent is still Active despite reaching a standard End node, another active path (parallel split, unfinished MNI instance, stuck queue) hasn't completed. Check the Process Details diagram in the Monitor tab to find it.
Hello Shubham Aware There is no parallel path in a process model and i have used start process with MNI.Coming Stuck Queue how can i check it, because it has been triggered yesterday and after that many process models got triggered and competed why would only this PM in queue
My guess, likely one MNI instance errored or paused by exception, so All instances are done never triggers completion.