MID Servers down after cloningIssue MID Servers went down after cloningReleaseXanadu Patch 1 Hot Fix 3bCauseThe root cause of the problem is that the mid-server user credentials are not updated after the cloning process, causing the mid-servers to go down. Additionally, the mid-server user is locked out.Resolution1. Please validate that the user credentials are correct, and update the mid-server user credentials on the affected instances if needed.2. Unlock the mid-server user on the affected instances.3. If needed, reset the password for the mid-server user on the affected instances.4. Restart the affected mid servers on the affected instances.After performing these steps, the mid servers should be up and running.**Additional Information:**Please review the following knowledge base article for more important information on MID Servers and Clones: https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0786475