Default Orchestration Mid Server for workflow activitySummaryWe were expecting the mid server orchestration selection is based on the IP range, capability, if both met, then a random mid server with status "Up" and Validated "Yes" will be selected. In our tested we found the mid server keeps using the default Orchestration Mid Server, even if the default mid sever was down and not validated. When we removed the default mid server, and the orchestration job just simply fail with no error.InstructionsFor a custom activity, if target host is a DNS name, which is resolved to multiple IPs, only default MID server can be used. Workaround: Add AD FQDN name (ie: server02.lab02.com) to table "cmdb_ci_dns_name" and add in ip addresses for the AD When target host is FQDN and cmdb_ci_dns_name is not set, then only default MID server is used.When target host is FQDN and cmdb_ci_dns_name is set, and default MID server is set, random MID server is used.When target host is FQDN and cmdb_ci_dns_name is set, and default MID server is not set, random MID server is used.