https://community.appian.com/discussions/f/process/34908/regarding-unattended-node-assignmentScenario: The user started the process and before process completes user left the bank .The sub process got errored because assignment of nodes is &#39;run as whoever started the process&#39;. In this scenario , do we need to change assignment of that node toen-USTelligent Community 12https://community.appian.com/thread/135236?ContentTypeID=1Mon, 13 May 2024 13:29:15 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:7771dd21-f2f6-4fe7-8cb9-94c66705722eMike Schmitt<p>This is something that has to be more carefully planned than most newer devs realized, when there is even the slightest chance a process instance started by a user will ever outlive their active status.</p> <p>However unlike in the older days, there&#39;s currently a reasonable work-around in case it does happen, particularly if a deactivated user is the initator of longer-lived instance that needs to stay active (and not breaking) for whatever reason.&nbsp; Note that this workaround is only remedial, it shouldn&#39;t be something your process is initially designed for (but instead should be designed to avoid the need for this...)</p> <p>Take the deactivated user account - reactivate it, but then rename it (particularly the username) to something indicating that they&#39;re a deactivated user.&nbsp; Then I&#39;ll usually change the &quot;last name&quot; field from whatever it was, to &quot;Service Account&quot;.&nbsp; Then add it to the Service Accounts system group (and remove the email address associated with the account).&nbsp; This both prevents the account from ever auto-deactivating, while 100% preventing the original owner of the account from getting back into it.</p><div style="clear:both;"></div>https://community.appian.com/thread/135232?ContentTypeID=1Mon, 13 May 2024 12:31:47 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:4cbedcaf-2e05-46d2-b3e4-5c3f61cb4ee4navinkumars<p>I want to mention one thing. Whenever a PM is imported into a environment, the user who performs the import is assumed as the designer. In my project it is requested always to use &quot;run as whoever designed&quot;. So, whenever a PM is imported to production they will use a service account user(a user who will never gets deactivated). So in any case we won&#39;t get any error.<br /><br />Additionally I would recommend a post that may help your question:&nbsp;<a href="https://community.appian.com/discussions/f/best-practices/13547/run-as-whoever-designed-the-model">community.appian.com/.../run-as-whoever-designed-the-model</a></p><div style="clear:both;"></div>https://community.appian.com/thread/134915?ContentTypeID=1Wed, 08 May 2024 05:35:10 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:4ee4a9dd-8073-49b1-82c6-b8bb55fada41Stefan Helzle<p>My approach to this, is to not disable the user account in Appian. Assuming that you have SSO in place, that user cannot log in anyways.</p> <p>Disabling account should only be done when there are no active process instances anymore.</p><div style="clear:both;"></div>