<h2>Use mid server cluster in Soap message definition if the assigned mid server is in failover configuration</h2><br/><div style="overflow-x:auto"><ul><li>Since there is no option to give the cluster name and only have mid server in the soap message, the cluster definition will automatically take and use other mid server from the cluster definition if the first one fails<br /><br /></li><li>MID Servers in a fail-over cluster each have a configured order that the platform uses to determine which MID Server to use next in case of failure. MID Servers in a fail-over cluster work independently and do not load balance with other MID Servers in that cluster (although they might also be members of load balancing clusters).<br /><br /></li><li>When a MID Server fails, the MID Server Cluster Management business rule selects the highest available MID Server in the order to take over the work. The selected MID Server checks the ECC Queue and starts with jobs that are either Processing or Ready<br /><br /></li><li>When the mid server defined is a part of the cluster and if it goes down the above Business rule will react and make sure other Server is used, We just have to make sure to configure the fail-over MID Server with at least the same capabilities as the MID Server it is intended to relieve.<br /><br /></li><li>Refer to <a href="https://docs.servicenow.com/csh?topicname=t_ConfigureAMIDServerCluster.html&version=latest">Configure a MID Server cluster</a> for more details</li></ul></div>