https://community.appian.com/support/w/kb/1295/kb-1838-the-sub-process-started-by-this-activity-has-been-deleted-errors-found-in-the-db_5f00_px-engine-logsen-USTelligent Community 12https://community.appian.com/support/w/kb/1295/kb-1838-the-sub-process-started-by-this-activity-has-been-deleted-errors-found-in-the-db_5f00_px-engine-logsMon, 14 Jan 2019 18:57:39 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:e062b14f-e166-4da2-801f-7f69154ac059Jordan Horwathttps://community.appian.com/support/w/kb/1295/kb-1838-the-sub-process-started-by-this-activity-has-been-deleted-errors-found-in-the-db_5f00_px-engine-logs#commentsCurrent Revision posted to Appian Knowledge Base by Jordan Horwat on 1/14/2019 6:57:39 PM<br /> <h2>Symptoms</h2> <p>In the <code>&lt;APPIAN_HOME&gt;/logs</code> directory, the <strong>db_PX*</strong> engine logs contain an error similar to the following one:</p> <pre>&quot;ERROR .a.noa &quot;Activity 1589: &#39;SUB_PROC&#39;, Process 2387: &#39;&lt;PROCESS_NAME&gt;&#39;, Node instance 1558: &#39;Email Notification&#39;&quot; &quot;Cause: The sub-process started by this activity has been deleted. Recommended Action: This node cannot complete. Please start the next node if necessary.&quot;&quot;</pre> <p>Administrators will also be notified of the error via an email notification. If the error is continuously printed in the engine logs, then email notifications can accumulate.</p> <h2>Cause</h2> <p>A sub-process with dependencies was deleted, causing the dependent processes to fail. This would likely happen after a process cleanup on the environment.</p> <h2>Action</h2> <p>Identify the problematic sub-processes from the <strong>db_PX*</strong> logs. On the front end, cancel all nodes referencing the deleted sub-process, and ensure that no new processes reference the deleted sub-process.</p> <h2>Affected Versions</h2> <p>This article applies to&nbsp;all versions of Appian.</p> <p>Last Reviewed: January 2019</p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: email, engines, infrastructure</div> https://community.appian.com/support/w/kb/1295/kb-1838-the-sub-process-started-by-this-activity-has-been-deleted-errors-found-in-the-db_5f00_px-engine-logs/revision/2Mon, 14 Jan 2019 13:55:18 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:e062b14f-e166-4da2-801f-7f69154ac059Jordan Horwathttps://community.appian.com/support/w/kb/1295/kb-1838-the-sub-process-started-by-this-activity-has-been-deleted-errors-found-in-the-db_5f00_px-engine-logs#commentsRevision 2 posted to Appian Knowledge Base by Jordan Horwat on 1/14/2019 1:55:18 PM<br /> <h2>Symptoms</h2> <p>In the <code>&lt;APPIAN_HOME&gt;/logs</code> directory, the <strong>db_PX*</strong> engine logs contain an error similar to the following one:</p> <pre>&quot;ERROR .a.noa &quot;Activity 1589: &#39;SUB_PROC&#39;, Process 2387: &#39;&lt;PROCESS_NAME&gt;&#39;, Node instance 1558: &#39;Email Notification&#39;&quot; &quot;Cause: The sub-process started by this activity has been deleted. Recommended Action: This node cannot complete. Please start the next node if necessary.&quot;&quot;</pre> <p>Administrators will also be notified of the error via an email notification. If the error is continuously printed in the engine logs, then email notifications can accumulate.</p> <h2>Cause</h2> <p>A sub-process with dependencies was deleted, causing the dependent processes to fail. This would likely happen after a process cleanup on the environment.</p> <h2>Action</h2> <p>Identify the problematic sub-processes from the <strong>db_PX</strong> logs. On the front end, cancel all nodes referencing the deleted sub-process, and ensure that no new processes reference the deleted sub-process.</p> <h2>Affected Versions</h2> <p>This article applies to&nbsp;all versions of Appian.</p> <p>Last Reviewed: January 2019</p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: email, engines, infrastructure</div> https://community.appian.com/support/w/kb/1295/kb-1838-the-sub-process-started-by-this-activity-has-been-deleted-errors-found-in-the-db_5f00_px-engine-logs/revision/1Tue, 08 Jan 2019 20:23:54 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:e062b14f-e166-4da2-801f-7f69154ac059Khalil Ben Naceurhttps://community.appian.com/support/w/kb/1295/kb-1838-the-sub-process-started-by-this-activity-has-been-deleted-errors-found-in-the-db_5f00_px-engine-logs#commentsRevision 1 posted to Appian Knowledge Base by Khalil Ben Naceur on 1/8/2019 8:23:54 PM<br /> <h2>Symptoms</h2> <p>In the <code>&lt;APPIAN_HOME&gt;/logs</code> directory, the <strong>db_PX</strong> engine logs contain an error similar to the following one:</p> <p><code>&quot;ERROR .a.noa &quot;Activity 1589: &#39;SUB_PROC&#39;, Process 2387: &#39;&lt;PROCESS_NAME&gt;&#39;, Node instance 1558: &#39;Email Notification&#39;&quot; &quot;Cause: The sub-process started by this activity has been deleted. Recommended Action: This node cannot complete. Please start the next node if necessary.&quot;&quot;</code></p> <p>Administrators will also be notified of the error via an email notification. If the error is continuously printed in the engine logs, then email notifications can accumulate.</p> <h2>Cause</h2> <p>A sub-process with dependencies was deleted, causing the dependent processes to fail. This would likely happen after a process cleanup on the environment.</p> <h2>Action</h2> <p>Identify the problematic sub-processes from the <strong>db_PX</strong> logs. On the front end, cancel all nodes referencing the deleted sub-process, and ensure that no new processes reference the deleted sub-process.</p> <h2>Affected Versions</h2> <p>This article applies to&nbsp;all versions of Appian.</p> <p>Last Reviewed: January 2019</p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: email, engines</div>