MID Server active issues The ServiceNow® instance has a dedicated table that publishes active issues with MID Servers and alerts administrators when a MID Server is in danger of exceeding its resources. The MID Server Issue [ecc_agent_issue] table displays a number of common issues that a MID Server can experience, as they occur. Error checking processes attempt to pinpoint the most likely cause of the issue. Informative error messages name the affected MID Server and explain the possible cause of the issue. The ecc_agent_issue table retains its records for 30 days. To access records in this table, navigate to MID Server > Server Issues. Supported MID Server active issues: Bad user credentials after instance cloning. Approaching resource thresholds for CPU usage and JVM memory. Errors detected during pre-upgrade testing. User authentication and authorization failures. Network connectivity interruptions and role configuration errors. Figure 1. Example MID Server Issue record Active MID Server post-cloning credential issuesThe system provides automatic processes to detect and notify you of possible MID Server credential issues after instance cloning.MID Server resource threshold alertsThe instance displays warnings when a MID Server breaches its resource thresholds for CPU and JVM memory usage, enabling users to create email notifications or custom scripts when a breach occurs.MID Server user connectivity issuesThe instance writes issues involving MID Server user logins and network connectivity to the MID Server Issue [ecc_agent_issue] table and creates events you can use in custom scripts or to send email notifications.