Mid server running but displaying the error "MID Server not operational (status: Down), possibly due to recent clone."Issue Once the customer has cloned the development instance recently the MID servers would be running but would display below error in the MID Server Issues tab: MID Server not operational (status: Down), possibly due to recent clone. Verify credentials for logged on user '********'.ResolutionThis is due to the fact that the source MID Server user credentials copied into the target instance might not match those used by the existing set of MID Servers used by the target. You can view the related documentation below:https://docs.servicenow.com/csh?topicname=mid-post-clone-issue-resolution.html&version=latestThe resolution to this issue would be to perform the below actions:1) Stop the current MID Server windows service.2) Go to the MID server /agent/ folder and open the config.xml file with a text editor such as WordPad.3) Enter the MID user credentials in the mid.instance.username and mid.instance.password parameters.4) Start the MID Server windows service.