MID Server shows “AMB client disconnected after connecting” after upgrade to Australia

deebika019
Tera Contributor

After upgrading our ServiceNow instance to the Australia release, we are observing an issue with the MID Server.

  • MID Server is Up and Validated
  • Latest MID version (Australia) is installed
  • MID is refreshing normally (Last refreshed: May 27, 2026)

However, under MID Server Issues, the following error is still displayed:

AMB client disconnected after connecting

 

observations:

  • The error was last detected on May 23, 2026
  • No additional occurrences observed after that
  • Restarted the MID Server, but the issue record is still visible
  • Threads and AMB client processes appear to be running normally
  • MID is deployed in a customer network environment (behind firewall/proxy)

 

Actions Taken:

  • Restarted MID Server service
  • Verified MID Server version compatibility
  • Checked MID status and refresh (working fine)
  • Reviewed threads → AMB-related threads present
  • Verified that issue is not continuously increasing

Additional Question:

If this needs to be fixed, what further troubleshooting steps should be performed beyond:

  • Checking agent logs
  • Validating WebSocket / proxy configuration
  • Reviewing SSL/certificate setup
0 REPLIES 0