https://community.appian.com/support/w/kb/2017/kb-2158-process-variables-unexpectedly-set-to-null-after-asynchronous-sub-process-runsen-USTelligent Community 12https://community.appian.com/support/w/kb/2017/kb-2158-process-variables-unexpectedly-set-to-null-after-asynchronous-sub-process-runsTue, 20 Oct 2020 17:00:24 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:cbb7c311-7d9e-4e8f-bc8a-000e594693f6Elly Menghttps://community.appian.com/support/w/kb/2017/kb-2158-process-variables-unexpectedly-set-to-null-after-asynchronous-sub-process-runs#commentsCurrent Revision posted to Appian Knowledge Base by Elly Meng on 10/20/2020 5:00:24 PM<br /> <h2>Symptoms</h2> <p>Process variables are unexpectedly set to null after an <a href="https://docs.appian.com/suite/help/latest/Sub-Process_Activity.html#asynchronous-sub-processes">asynchronous sub-process</a> node completes, even though non-null output is expected:<br /><br /><img alt=" " border="0" src="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-00-11/ErrorLog.png" /></p> <h2>Cause</h2> <p><span>The <a href="https://docs.appian.com/suite/help/latest/Sub-Process_Activity.html#asynchronous-sub-processes">asynchronous sub-process</a> has output variables that were not deleted because it was once <a href="https://docs.appian.com/suite/help/latest/Sub-Process_Activity.html#synchronous-sub-processes">synchronous</a>. When the process became asynchronous, the output variables became hidden but&nbsp;were not removed. This caused the parent process variables mapped to the output variables to become nullified instead of remaining unchanged after the asynchronous process ran. This issue has been reported to the Appian Product Team&nbsp;with reference number&nbsp;<strong>AN-96059</strong>.</span></p> <h2>Workaround</h2> <ol> <li><span>Convert</span> the&nbsp;sub-process&nbsp;back<span> to synchronous.</span></li> <li><span>Remove&nbsp;the&nbsp;output variables.</span></li> <li><span>Convert the sub-process back to asynchronous.</span><span></span></li> </ol> <h2>Affected Versions</h2> <p>This article applies to all versions of Appian.</p> <p><span style="font-family:inherit;">Last Reviewed: October 2020</span></p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: known issues, process modeler, process models, application design, processes, open issues</div> https://community.appian.com/support/w/kb/2017/kb-2158-process-variables-unexpectedly-set-to-null-after-asynchronous-sub-process-runs/revision/9Tue, 20 Oct 2020 17:00:24 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:cbb7c311-7d9e-4e8f-bc8a-000e594693f6Elly Menghttps://community.appian.com/support/w/kb/2017/kb-2158-process-variables-unexpectedly-set-to-null-after-asynchronous-sub-process-runs#commentsRevision 9 posted to Appian Knowledge Base by Elly Meng on 10/20/2020 5:00:24 PM<br /> <h2>Symptoms</h2> <p>Process variables are unexpectedly set to null after an <a href="https://docs.appian.com/suite/help/latest/Sub-Process_Activity.html#asynchronous-sub-processes">asynchronous sub-process</a> node completes, even though non-null output is expected:<br /><br /><img alt=" " border="0" src="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-00-13/ErrorLog.png" /></p> <h2>Cause</h2> <p><span>The <a href="https://docs.appian.com/suite/help/latest/Sub-Process_Activity.html#asynchronous-sub-processes">asynchronous sub-process</a> has output variables that were not deleted because it was once <a href="https://docs.appian.com/suite/help/latest/Sub-Process_Activity.html#synchronous-sub-processes">synchronous</a>. When the process became asynchronous, the output variables became hidden but&nbsp;were not removed. This caused the parent process variables mapped to the output variables to become nullified instead of remaining unchanged after the asynchronous process ran. This issue has been reported to the Appian Product Team&nbsp;with reference number&nbsp;<strong>AN-96059</strong>.</span></p> <h2>Workaround</h2> <ol> <li><span>Convert</span> the&nbsp;sub-process&nbsp;back<span> to synchronous.</span></li> <li><span>Remove&nbsp;the&nbsp;output variables.</span></li> <li><span>Convert the sub-process back to asynchronous.</span><span></span></li> </ol> <h2>Affected Versions</h2> <p>This article applies to all versions of Appian.</p> <p><span style="font-family:inherit;">Last Reviewed: October 2020</span></p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: known issues, process modeler, process models, application design, processes, open issues</div> https://community.appian.com/support/w/kb/2017/kb-2158-process-variables-unexpectedly-set-to-null-after-asynchronous-sub-process-runs/revision/8Tue, 20 Oct 2020 16:58:15 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:cbb7c311-7d9e-4e8f-bc8a-000e594693f6Elly Menghttps://community.appian.com/support/w/kb/2017/kb-2158-process-variables-unexpectedly-set-to-null-after-asynchronous-sub-process-runs#commentsRevision 8 posted to Appian Knowledge Base by Elly Meng on 10/20/2020 4:58:15 PM<br /> <h2>Symptoms</h2> <p>Process variables are unexpectedly set to null after an <a href="https://docs.appian.com/suite/help/latest/Sub-Process_Activity.html#asynchronous-sub-processes">asynchronous sub-process</a> node completes, even though non-null output is expected:<br /><br /><img alt=" " border="0" src="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-00-13/ErrorLog.png" /></p> <h2>Cause</h2> <p><span>The <a href="https://docs.appian.com/suite/help/latest/Sub-Process_Activity.html#asynchronous-sub-processes">asynchronous sub-process</a> has output variables that were not deleted because it was once <a href="https://docs.appian.com/suite/help/latest/Sub-Process_Activity.html#synchronous-sub-processes">synchronous</a>. When the process became asynchronous, the output variables became hidden but&nbsp;were not removed. This caused the parent process variables mapped to the output variables to become nullified instead of remaining unchanged after the asynchronous process ran. This issue has been reported to the Appian Product Team&nbsp;with reference number&nbsp;<strong>AN-96059</strong>.</span></p> <h2>Workaround</h2> <ol> <li><span>Convert</span> the&nbsp;sub-process&nbsp;back<span> to synchronous.</span></li> <li><span>Remove&nbsp;the&nbsp;output variables.</span></li> <li><span>Convert the sub-process back to asynchronous.</span><span></span></li> </ol> <h2>Affected Versions</h2> <p>This article applies to all versions of Appian.</p> <p><span style="font-family:inherit;">Last Reviewed: October 2020</span></p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: known issues, process modeler, process models, application design, processes, open issues</div> https://community.appian.com/support/w/kb/2017/kb-2158-process-variables-unexpectedly-set-to-null-after-asynchronous-sub-process-runs/revision/7Tue, 20 Oct 2020 16:57:00 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:cbb7c311-7d9e-4e8f-bc8a-000e594693f6Elly Menghttps://community.appian.com/support/w/kb/2017/kb-2158-process-variables-unexpectedly-set-to-null-after-asynchronous-sub-process-runs#commentsRevision 7 posted to Appian Knowledge Base by Elly Meng on 10/20/2020 4:57:00 PM<br /> <h2>Symptoms</h2> <p>Process variables are unexpectedly set to null after an <a href="https://docs.appian.com/suite/help/latest/Sub-Process_Activity.html#asynchronous-sub-processes">asynchronous sub-process</a> node completes, even though non-null output is expected:</p> <p><br /><img alt=" " border="0" src="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-00-13/ErrorLog.png" /></p> <h2>Cause</h2> <p><span>The <a href="https://docs.appian.com/suite/help/latest/Sub-Process_Activity.html#asynchronous-sub-processes">asynchronous sub-process</a> has output variables that were not deleted because it was once <a href="https://docs.appian.com/suite/help/latest/Sub-Process_Activity.html#synchronous-sub-processes">synchronous</a>. When the process became asynchronous, the output variables became hidden but&nbsp;were not removed. This caused the parent process variables mapped to the output variables to become nullified instead of remaining unchanged after the asynchronous process ran. This issue has been reported to the Appian Product Team&nbsp;with reference number&nbsp;<strong>AN-96059</strong>.</span></p> <h2>Workaround</h2> <ol> <li><span>Convert</span> the&nbsp;sub-process&nbsp;back<span> to synchronous.</span></li> <li><span>Remove&nbsp;the&nbsp;output variables.</span></li> <li><span>Convert the sub-process back to asynchronous.</span><span></span></li> </ol> <h2>Affected Versions</h2> <p>This article applies to all versions of Appian.</p> <p><span style="font-family:inherit;">Last Reviewed: October 2020</span></p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: known issues, process modeler, process models, application design, processes, open issues</div> https://community.appian.com/support/w/kb/2017/kb-2158-process-variables-unexpectedly-set-to-null-after-asynchronous-sub-process-runs/revision/6Fri, 16 Oct 2020 20:50:38 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:cbb7c311-7d9e-4e8f-bc8a-000e594693f6Zach Puderbachhttps://community.appian.com/support/w/kb/2017/kb-2158-process-variables-unexpectedly-set-to-null-after-asynchronous-sub-process-runs#commentsRevision 6 posted to Appian Knowledge Base by Zach Puderbach on 10/16/2020 8:50:38 PM<br /> <h2>Symptoms</h2> <p>Process variables are unexpectedly set to null after an <a href="https://docs.appian.com/suite/help/latest/Sub-Process_Activity.html#asynchronous-sub-processes">asynchronous sub-process</a> node completes, even though non-null output is expected:<br /><img alt=" " border="0" src="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-00-13/ErrorLog.png" /></p> <h2>Cause</h2> <p><span>The <a href="https://docs.appian.com/suite/help/latest/Sub-Process_Activity.html#asynchronous-sub-processes">asynchronous sub-process</a> has output variables that were not deleted because it was once <a href="https://docs.appian.com/suite/help/latest/Sub-Process_Activity.html#synchronous-sub-processes">synchronous</a>. When the process became asynchronous, the output variables became hidden but&nbsp;were not removed. This caused the parent process variables mapped to the output variables to become nullified instead of remaining unchanged after the asynchronous process ran. This issue has been reported to the Appian Product Team&nbsp;with reference number&nbsp;<strong>AN-96059</strong>.</span></p> <h2>Workaround</h2> <ol> <li><span>Convert</span> the&nbsp;sub-process&nbsp;back<span> to synchronous.</span></li> <li><span>Remove&nbsp;the&nbsp;output variables.</span></li> <li><span>Convert the sub-process back to asynchronous.</span><span></span></li> </ol> <h2>Affected Versions</h2> <p>This article applies to all versions of Appian.</p> <p><span style="font-family:inherit;">Last Reviewed:&nbsp;September&nbsp;2020</span></p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: known issues, process modeler, process models, application design, processes, open issues</div> https://community.appian.com/support/w/kb/2017/kb-2158-process-variables-unexpectedly-set-to-null-after-asynchronous-sub-process-runs/revision/5Sat, 12 Sep 2020 22:09:10 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:cbb7c311-7d9e-4e8f-bc8a-000e594693f6Elly Menghttps://community.appian.com/support/w/kb/2017/kb-2158-process-variables-unexpectedly-set-to-null-after-asynchronous-sub-process-runs#commentsRevision 5 posted to Appian Knowledge Base by Elly Meng on 9/12/2020 10:09:10 PM<br /> <h2>Symptoms</h2> <p>Process variables are unexpectedly set to null after an <a href="https://docs.appian.com/suite/help/latest/Sub-Process_Activity.html#asynchronous-sub-processes">asynchronous sub-process</a> node completes, even though non-null output is expected:<br /><img alt=" " src="/resized-image/__size/0x240/__key/communityserver-wikis-components-files/00-00-00-00-13/Asyncronousstuff.png" /></p> <h2>Cause</h2> <p><span>The <a href="https://docs.appian.com/suite/help/latest/Sub-Process_Activity.html#asynchronous-sub-processes">asynchronous sub-process</a> has output variables that were not deleted because it was once <a href="https://docs.appian.com/suite/help/latest/Sub-Process_Activity.html#synchronous-sub-processes">synchronous</a>. When the process became asynchronous, the output variables became hidden but&nbsp;were not removed. This caused the parent process variables mapped to the output variables to become nullified instead of remaining unchanged after the asynchronous process ran. This issue has been reported to the Appian Product Team&nbsp;with reference number&nbsp;<strong>AN-96059</strong>.</span></p> <h2>Workaround</h2> <ol> <li><span>Convert</span> the&nbsp;sub-process&nbsp;back<span> to synchronous.</span></li> <li><span>Remove&nbsp;the&nbsp;output variables.</span></li> <li><span>Convert the sub-process back to asynchronous.</span><span></span></li> </ol> <h2>Affected Versions</h2> <p>This article applies to all versions of Appian.</p> <p><span style="font-family:inherit;">Last Reviewed:&nbsp;September&nbsp;2020</span></p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: known issues, process modeler, process models, application design, processes, open issues</div> https://community.appian.com/support/w/kb/2017/kb-2158-process-variables-unexpectedly-set-to-null-after-asynchronous-sub-process-runs/revision/4Sat, 12 Sep 2020 22:07:38 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:cbb7c311-7d9e-4e8f-bc8a-000e594693f6Elly Menghttps://community.appian.com/support/w/kb/2017/kb-2158-process-variables-unexpectedly-set-to-null-after-asynchronous-sub-process-runs#commentsRevision 4 posted to Appian Knowledge Base by Elly Meng on 9/12/2020 10:07:38 PM<br /> <h2>Symptoms</h2> <p>Process variables are unexpectedly set to null after an <a href="https://docs.appian.com/suite/help/latest/Sub-Process_Activity.html#asynchronous-sub-processes">asynchronous sub-process</a> node completes, even though non-null output is expected:<br /><img alt=" " src="/resized-image/__size/0x240/__key/communityserver-wikis-components-files/00-00-00-00-13/Asyncronousstuff.png" /></p> <h2>Cause</h2> <p><span>The <a href="https://docs.appian.com/suite/help/latest/Sub-Process_Activity.html#asynchronous-sub-processes">asynchronous sub-process</a> has output variables that were not deleted because it was once <a href="https://docs.appian.com/suite/help/latest/Sub-Process_Activity.html#synchronous-sub-processes">synchronous</a>. When the process became asynchronous, the output variables became hidden but&nbsp;were not removed. This caused the parent process variables mapped to the output variables to become nullified instead of remaining unchanged after the asynchronous process ran. This issue has been reported to the Appian Product Team&nbsp;with reference number&nbsp;<strong>AN-96059</strong>.</span></p> <h2>Workaround</h2> <ol> <li><span>Convert</span> the&nbsp;sub-process&nbsp;back<span> to synchronous.</span></li> <li><span>Remove&nbsp;the&nbsp;output variables.</span></li> <li><span>Convert the sub-process back to asynchronous.</span><span></span></li> </ol> <h2>Affected Versions</h2> <p>This article applies to all versions of Appian.</p> <p><span style="font-family:inherit;">Last Reviewed:&nbsp;September&nbsp;2020</span></p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: known issues, application design, open issues</div> https://community.appian.com/support/w/kb/2017/kb-2158-process-variables-unexpectedly-set-to-null-after-asynchronous-sub-process-runs/revision/3Sat, 12 Sep 2020 22:05:00 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:cbb7c311-7d9e-4e8f-bc8a-000e594693f6Elly Menghttps://community.appian.com/support/w/kb/2017/kb-2158-process-variables-unexpectedly-set-to-null-after-asynchronous-sub-process-runs#commentsRevision 3 posted to Appian Knowledge Base by Elly Meng on 9/12/2020 10:05:00 PM<br /> <h2>Symptoms</h2> <p>Process variables are unexpectedly set to null after an <a href="https://docs.appian.com/suite/help/latest/Sub-Process_Activity.html#asynchronous-sub-processes">asynchronous sub-process</a> node completes, even though non-null output is expected:<br /><img alt=" " src="/resized-image/__size/0x240/__key/communityserver-wikis-components-files/00-00-00-00-13/Asyncronousstuff.png" /></p> <h2>Cause</h2> <p><span>The <a href="https://docs.appian.com/suite/help/latest/Sub-Process_Activity.html#asynchronous-sub-processes">asynchronous sub-process</a> has output variables that were not deleted because it was once <a href="https://docs.appian.com/suite/help/latest/Sub-Process_Activity.html#synchronous-sub-processes">synchronous</a>. When the process became asynchronous, the output variables became hidden but&nbsp;were not removed. This caused&nbsp;parent process variables mapped to the output variables to become nullified instead of remaining unchanged after the asynchronous process ran. This issue has been reported to the Appian Product Team&nbsp;with reference number&nbsp;<strong>AN-96059</strong>.</span></p> <h2>Workaround</h2> <ol> <li><span>Convert the&nbsp;<span style="font-size:12px;">sub-process</span>&nbsp;back to synchronous.</span></li> <li><span>Remove&nbsp;the&nbsp;output variables.</span></li> <li><span>Convert the sub-process back to asynchronous.</span><span></span></li> </ol> <h2>Affected Versions</h2> <p>This article applies to all versions of Appian.</p> <p><span style="font-family:inherit;">Last Reviewed:&nbsp;September&nbsp;2020</span></p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: known issues, application design, open issues</div> https://community.appian.com/support/w/kb/2017/kb-2158-process-variables-unexpectedly-set-to-null-after-asynchronous-sub-process-runs/revision/2Thu, 27 Aug 2020 00:31:17 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:cbb7c311-7d9e-4e8f-bc8a-000e594693f6Zach Puderbachhttps://community.appian.com/support/w/kb/2017/kb-2158-process-variables-unexpectedly-set-to-null-after-asynchronous-sub-process-runs#commentsRevision 2 posted to Appian Knowledge Base by Zach Puderbach on 8/27/2020 12:31:17 AM<br /> <h2>Symptoms</h2> <p>Process variables unexpectedly appear null after an <a href="https://docs.appian.com/suite/help/latest/Sub-Process_Activity.html#asynchronous-sub-processes">asynchronous sub-process</a> node completes, even though non-null output is expected:<br /><img alt=" " src="/resized-image/__size/0x240/__key/communityserver-wikis-components-files/00-00-00-00-13/Asyncronousstuff.png" /></p> <h2>Cause</h2> <p><span>The <a href="https://docs.appian.com/suite/help/latest/Sub-Process_Activity.html#asynchronous-sub-processes">asynchronous sub-process</a> was once <a href="https://docs.appian.com/suite/help/latest/Sub-Process_Activity.html#synchronous-sub-processes">synchronous</a> and had an output variable that was not deleted. The output variable was not removed when the process became asynchronous.&nbsp;This issue has been reported to the Appian Product Team. The reference number for this issue is <strong>AN-96059</strong>.</span></p> <h2>Workaround</h2> <ol> <li><span>Convert the <span style="font-size:12px;">sub-process</span>&nbsp;to synchronous.</span></li> <li><span>Remove the output variable.</span></li> <li><span>Convert back to asynchronous.</span><span></span></li> </ol> <h2>Affected Versions</h2> <p>This article applies to all versions of Appian.</p> <p><span style="font-family:inherit;">Last Reviewed: August 2020</span></p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: known issues, application design, open issues</div> https://community.appian.com/support/w/kb/2017/kb-2158-process-variables-unexpectedly-set-to-null-after-asynchronous-sub-process-runs/revision/1Thu, 27 Aug 2020 00:28:36 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:cbb7c311-7d9e-4e8f-bc8a-000e594693f6Zach Puderbachhttps://community.appian.com/support/w/kb/2017/kb-2158-process-variables-unexpectedly-set-to-null-after-asynchronous-sub-process-runs#commentsRevision 1 posted to Appian Knowledge Base by Zach Puderbach on 8/27/2020 12:28:36 AM<br /> <h2>Symptoms</h2> <p>Process variables unexpectedly appear null after an asynchronous sub-process node completes, even though non-null output is expected:<br /><img alt=" " src="/resized-image/__size/0x240/__key/communityserver-wikis-components-files/00-00-00-00-13/Asyncronousstuff.png" /></p> <h2>Cause</h2> <p><span>The asynchronous sub-process was once synchronous and had an output variable that was not deleted. The output variable was not removed when the process became asynchronous.&nbsp;This issue has been reported to the Appian Product Team. The reference number for this issue is <strong>AN-96059</strong>.</span></p> <h2>Workaround</h2> <ol> <li><span>Convert the subprocess to synchronous.</span></li> <li><span>Remove the output variable.</span></li> <li><span>Convert back to asynchronous.</span><span></span></li> </ol> <h2>Affected Versions</h2> <p>This article applies to all versions of Appian.</p> <p><span style="font-family:inherit;">Last Reviewed: August 2020</span></p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: known issues, application design, open issues</div>