If default Mid Server Override is customized, after instance is upgraded to Madrid release, MID Server Selection is broken for Cloud Discovery / Cloud Account DiscoveryDescriptionIf default Mid Server Override is customized, after instance is upgraded to Madrid release, MID Server Selection is broken for Cloud Discovery / Cloud Account Discovery. For example, on a cloud service account, if clicking on "Discovery Datacenter", error message shows: "Cloud not resolve mid server for API request".CauseIn the OOB Mid Server Override: "Override by capability", the variable name for "context" has been changed to "midSelectorContext". For example: London: (function filter(/* MIDServerJS Array */ candidateMIDList, /* MIDServerJS Array */ defaultSelectedMIDList, /* Native JS object */ context, /* MIDSelectorParamJS */ requestedParameters) .. })(candidateMIDList, defaultSelectedMIDList, context, requestedParameters); Madrid: (function filter(/* MIDServerJS Array */ candidateMIDList, /* MIDServerJS Array */ defaultSelectedMIDList, /* Native JS object */ midSelectorContext, /* MIDSelectorParamJS */ requestedParameters) ... })(candidateMIDList, defaultSelectedMIDList, midSelectorContext, requestedParameters);ResolutionPlease review the custom script and make sure the name of the variables are correct.