When MID Server restarts, ACC doesn't connect to MID again.Issue <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } When MID Server restarts, collected ACC agent will reconnect to MID but some agents don't reconnect to the MID again. Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } All Resolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } - ACC reconnect to the MID after nslookup command gets result. - acc.log have nslookup <MID Server host_name> output: when result is returned like below. Pattern A (nslookup command gets correct results): 2025-06-19T08:52:59.21 [INFO] [agent] attempting to run nslookup on last connected MID server url, parsing hostname out of url wss://192.168.1.100:8443/ws/events 2025-06-19T08:52:59.26 [INFO] [agent] nslookup 192.168.1.100 output: 100.1.168.192.in-addr.arpa name = ip-192.168-1-100.internal. Authoritative answers can be found from: Pattern B (no nslookup command): 2025-06-19T08:45:06.54 [INFO] [agent] attempting to run nslookup on last connected MID server url, parsing hostname out of url wss://sample-mid:8443/ws/events 2025-06-19T08:45:06.55 [ERROR] [agent] error running nslookup sample-mid: exec: "nslookup": executable file not found in $PATH 2025-06-19T08:45:06.55 [INFO] [agent] nslookup sample-mid output: Pattern C (Can't connect to DNS): 2025-06-19T08:40:14.68 [INFO] [agent] attempting to run nslookup on last connected MID server url, parsing hostname out of url wss://sample-mid:8443/ws/events 2025-06-19T08:40:29.71 [ERROR] [agent] error running nslookup sample-mid: exit status 1 2025-06-19T08:40:29.72 [INFO] [agent] nslookup sample-mid output: ;; connection timed out; no servers could be reached Pattern D (nslookup command gets NXDOMAIN error) 2025-06-19T08:31:00.33 [INFO] [agent] attempting to run nslookup on last connected MID server url, parsing hostname out of url wss://sample-mid:8443/ws/events 2025-06-19T08:31:00.36 [ERROR] [agent] error running nslookup sample-mid: exit status 1 2025-06-19T08:31:00.37 [INFO] [agent] nslookup sample-mid output: Server: 192.168.0.2 Address: 192.168.0.2#53 ** server can't find sample-mid: NXDOMAIN - When above output log is not shown on acc.log, nslookup command stucks and doesn't return result like "trying next server" status. Customer needs to check OS side for this issue.