Discovery Schedules show a "MID server", even though "MID Server cluster" is setIssue Discovery Schedules show a "MID server" in the discovery_schedule.LIST, even though the "MID Server cluster" is set Steps to Reproduce:- Login into the instance- Create a schedule using a specific MID Server.- Modified the above-created schedule to use MID Server Cluster.- In the back end "MID Server" field value is not getting cleared.ReleaseSan Diego, TokyoResolution- If Cluster is selected, then the MID Server field value is ignored by the shazzam launch code that runs when a discovery schedule starts - This is not breaking anything - You could create a simple UI policy with an action to clear the MID Server field when the Mid Server Selection Method choice field changes to the cluster Please check the below document for your reference https://docs.servicenow.com/bundle/sandiego-platform-administration/page/administer/form-administration/task/t_CreateAUIPolicy.html