Legacy "Run PowerShell" Workflow activities do not fail-over to the non-default MID if it goes down.Issue <!-- div.margin { padding: 10px 40px 40px 30px; } table.tocTable { border: 1px solid; border-color: #e0e0e0; background-color: #fff; } .title { color: #d1232b; font-weight: normal; font-size: 28px; } h1 { color: #d1232b; font-weight: normal; font-size: 21px; margin-bottom: 5px; border-bottom-width: 2px; border-bottom-style: solid; border-bottom-color: #cccccc; } h2 { color: #646464; font-weight: bold; font-size: 18px; } h3 { color: #000000; font-weight: bold; font-size: 16px; } h4 { color: #666666; font-weight: bold; font-size: 15px; } h5 { color: #000000; font-weight: bold; font-size: 13px; } h6 { color: #000000; font-weight: bold; font-size:14px; } ul, ol { margin-left: 0; list-style-position: outside; } --> The Legacy "Run PowerShell" Workflow activities do not automatically fail-over to the non-default MID if it goes down. ResolutionThis is due to the logic in the MIDServerSelector Script Include:https://<instance_name>.service-now.com/nav_to.do?uri=sys_script_include.do?sys_id=97e984500a0006786e9c7e86128249a8 var defaultMidServer = GlideProperties.get("mid.server.rba_default"); if (!JSUtil.nil(defaultMidServer)) { var gr = new GlideRecord('ecc_agent'); gr.addQuery('name', defaultMidServer); gr.query(); if (!gr.next()) { this.errorMsg = 'The configured default MID server (' + defaultMidServer + ') is not valid'; defaultMidServer = ""; }} else this.errorMsg = 'There is no MID server configured to run this activity'; This "Run PowerShell" activity is deprecated and is unavailable for new workflows. To replace the functionality of this activity, use the Powershell activity template to create a custom, scoped activity. Related LinksPowershell Activities