KB-1319 After upgrade from 16.2 to 16.3 or 17.1, sub-processes are not starting on the latest version of the sub-process modelhttps://community.appian.com/support/w/kb/538/kb-1319-after-upgrade-from-16-2-to-16-3-or-17-1-sub-processes-are-not-starting-on-the-latest-version-of-the-sub-process-modelen-USTelligent Community 12KB-1319 After upgrade from 16.2 to 16.3 or 17.1, sub-processes are not starting on the latest version of the sub-process modelhttps://community.appian.com/support/w/kb/538/kb-1319-after-upgrade-from-16-2-to-16-3-or-17-1-sub-processes-are-not-starting-on-the-latest-version-of-the-sub-process-modelMon, 23 Jul 2018 03:53:33 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:b522d337-978e-453e-88b2-25d4b2373e18Parmida Borhanihttps://community.appian.com/support/w/kb/538/kb-1319-after-upgrade-from-16-2-to-16-3-or-17-1-sub-processes-are-not-starting-on-the-latest-version-of-the-sub-process-model#commentsCurrent Revision posted to Appian Knowledge Base by Parmida Borhani on 7/23/2018 3:53:33 AM<br /> <table style="background-color:#bcedaf;"> <tbody> <tr> <td>This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.</td> </tr> </tbody> </table> <h2 id="symptoms">Symptoms</h2> <p>After upgrade to 16.3 or 17.1 from 16.2 HF Package E or later, sub-processes do not always start&nbsp;on the latest version of the process model.</p> <p>There are no related errors in the application server log or alerts generated.</p> <h2>Cause</h2> <p>This issue&nbsp;has been resolved via&nbsp;<strong>AN-81845</strong> in the following Appian hotfixes/versions:</p> <ul> <li>Appian 16.3 Hotfix Package E</li> <li>Appian 17.1 Hotfix Package B</li> <li>Appian 17.2</li> </ul> <h2>Action</h2> <p>Apply the latest hotfix for your Appian version or upgrade to the latest version of Appian.</p> <h2>Workaround</h2> <p>Republish the parent process model and sub-process process model in that order.</p> <h2>Affected Versions</h2> <p>This article applies to Appian versions 16.3 and 17.1.</p> <p>Last Reviewed: July 2017</p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: known issues, process models, installation, application design, fixed issues, upgrade</div> KB-1319 After upgrade from 16.2 to 16.3 or 17.1, sub-processes are not starting on the latest version of the sub-process modelhttps://community.appian.com/support/w/kb/538/kb-1319-after-upgrade-from-16-2-to-16-3-or-17-1-sub-processes-are-not-starting-on-the-latest-version-of-the-sub-process-model/revision/10Thu, 13 Jul 2017 15:46:40 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:b522d337-978e-453e-88b2-25d4b2373e18Nick Vigilantehttps://community.appian.com/support/w/kb/538/kb-1319-after-upgrade-from-16-2-to-16-3-or-17-1-sub-processes-are-not-starting-on-the-latest-version-of-the-sub-process-model#commentsRevision 10 posted to Appian Knowledge Base by Nick Vigilante on 7/13/2017 3:46:40 PM<br /> <table style="background-color:#bcedaf;"> <tbody> <tr> <td>This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.</td> </tr> </tbody> </table> <h2 id="symptoms">Symptoms</h2> <p>After upgrade to 16.3 or 17.1 from 16.2 HF Package E or later, sub-processes do not always start&nbsp;on the latest version of the process model.</p> <p>There are no related errors in the application server log or alerts generated.</p> <h2>Cause</h2> <p>This issue&nbsp;has been resolved via&nbsp;<strong>AN-81845</strong> in the following Appian hotfixes/versions:</p> <ul> <li>Appian 16.3 Hotfix Package E</li> <li>Appian 17.1 Hotfix Package B</li> <li>Appian 17.2</li> </ul> <h2>Action</h2> <p>Apply the latest hotfix for your Appian version or upgrade to the latest version of Appian.</p> <h2>Workaround</h2> <p>Republish the parent process model and sub-process process model in that order.</p> <h2>Affected Versions</h2> <p>This article applies to Appian versions 16.3 and 17.1.</p> <p>Last Reviewed: July 2017</p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: known issues, process models, fixed issues, upgrade</div> KB-1319 After upgrade from 16.2 to 16.3 or 17.1, sub-processes are not starting on the latest version of the sub-process modelhttps://community.appian.com/support/w/kb/538/kb-1319-after-upgrade-from-16-2-to-16-3-or-17-1-sub-processes-are-not-starting-on-the-latest-version-of-the-sub-process-model/revision/9Thu, 30 Mar 2017 18:17:12 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:b522d337-978e-453e-88b2-25d4b2373e18Nick Vigilantehttps://community.appian.com/support/w/kb/538/kb-1319-after-upgrade-from-16-2-to-16-3-or-17-1-sub-processes-are-not-starting-on-the-latest-version-of-the-sub-process-model#commentsRevision 9 posted to Appian Knowledge Base by Nick Vigilante on 3/30/2017 6:17:12 PM<br /> <h2>Symptoms</h2> <p>After upgrade to 16.3 or 17.1 from 16.2 HF Package E or later, sub-processes do not always start&nbsp;on the latest version of the process model.</p> <p>There are no related errors in the application server log or alerts generated.</p> <h2>Cause</h2> <p>This issue has been reported to the Appian product team. The reference number for this issue is <strong>AN-79387</strong>.</p> <h2>Action</h2> <p>This issue was resolved in 16.3 Hotfix Package E and 17.1 Hotfix Package B.</p> <p>Please apply the latest Hotfix Package for your Appian version.</p> <h2>Workaround</h2> <p>Republish the parent process model and sub-process process model in that order.</p> <h2>Affected Versions</h2> <p>This article applies to Appian versions 16.3 and 17.1.</p> <p>Last Reviewed: March 2017</p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: known issues, process models, fixed issues, upgrade</div>