https://www.servicenow.com/community/community-central-forum/issue-with-mid-selection-in-connection-table/m-p/3352084#M4238 <P>In the <EM>sys_connection</EM> table, there is a field called MID Selection. I have noticed that when we select Auto-select MID server, the credentials fail. However, when we choose a specific MID server instead, it works, is strange.</P><P>&nbsp;</P><P>Has anyone else come across this issue? If yes, could you please share if there is any known solution or workaround for it?</P><P>&nbsp;</P><P>&nbsp;</P> Thu, 14 Aug 2025 11:26:30 GMT Amitoj Wadhera 2025-08-14T11:26:30Z https://www.servicenow.com/community/community-central-forum/issue-with-mid-selection-in-connection-table/m-p/3352084#M4238 <P>In the <EM>sys_connection</EM> table, there is a field called MID Selection. I have noticed that when we select Auto-select MID server, the credentials fail. However, when we choose a specific MID server instead, it works, is strange.</P><P>&nbsp;</P><P>Has anyone else come across this issue? If yes, could you please share if there is any known solution or workaround for it?</P><P>&nbsp;</P><P>&nbsp;</P> Thu, 14 Aug 2025 11:26:30 GMT https://www.servicenow.com/community/community-central-forum/issue-with-mid-selection-in-connection-table/m-p/3352084#M4238 Amitoj Wadhera 2025-08-14T11:26:30Z https://www.servicenow.com/community/community-central-forum/issue-with-mid-selection-in-connection-table/m-p/3362785#M4364 <P>I’ve run into this with MID Server selection before, especially when the ecc_queue logic isn't lining up with target credentials or IP ranges. One fix that worked for us was adjusting the Discovery Behavior settings and double-checking the IP-to-MID mapping in the MID Server records. Also worth confirming if the target is reachable from all MIDs—network paths can quietly break auto-selection.</P> Tue, 26 Aug 2025 16:46:57 GMT https://www.servicenow.com/community/community-central-forum/issue-with-mid-selection-in-connection-table/m-p/3362785#M4364 ashleyharve 2025-08-26T16:46:57Z