How to identify if Workflow activity is not honoring to use "Default MID Server to use for Orchestration Activities" Summary<!-- /*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: ; } } At times, we notice the orchestration workflow activity when run, it does not pick up the desired MID server which is set under "Default MID Server to use for Orchestration Activities" but using different MID server. However, It randomly picks up the available mid servers and complete the activity. This KB explains on how to identify if Workflow activity is not honoring to use "Default MID Server to use for Orchestration Activities" 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: ; } } Any Instructions<!-- /*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: ; } } For example, we consider following MID Servers 1) MID Server Name: MID1 This MID is set as "Default MID Server to use for Orchestration Activities" https://<instance name>.service-now.com/system_properties_ui.do?sysparm_title=Orchestration%20MID%20Server%20Properties&sysparm_category=Orchestration%20MID%20Server 2) MID Server Name: MID2 This MID is picked up for the orchestration activity instead of default MID server. 3) Next we turn on the following debugging property: glide.automation.nodelog.level and reproduce the issue i.e. submit catalog request and RITM gets created.To enable the property, navigate to sys_properties.LIST and create a new record with the following values; name = "glide.automation.nodelog.level"type = "string"value = "debug" 4) After setting above debug property, check node logs: DEBUG: MidSelector.selectAnyMidServer REQUEST: app=Orchestration, IPs=[10.x.x.x], capabilities=[{Capability: PowerShell, value: null}], status filter=degraded, domain=(domainID/username:null)DEBUG: MidSelector.getCandidatesBasedOnStatus REQUEST: app=Orchestration, IPs=[10.40.120.48], capabilities=[{Capability: PowerShell, value: null}], status filter=degraded, domain=(domainID/username:null)DEBUG: MidSelector.selectMidServersFromMidList RESULT: from Status filter: 6 of 7 MID ServersDEBUG: MidSelector.selectMidServersFromMidList RESULT: from Application filter: 6 of 7 MID ServersDEBUG: MidSelector.selectMidServersFromMidList RESULT: from IP Range filter: 6 of 7 MID Servers=[MID3, MID2, MID4, MID1, MID5, MID6]DEBUG: MidSelector.selectMidServersFromMidList RESULT: from Capability filter: 1 of 7 MID Servers=[MID2]DEBUG: MidSelector.getCandidatesBasedOnStatus RESULT: 1 of 7 MID Servers=[MID2]DEBUG: MidSelector.selectAnyMidServer RESULT: MID Server=MID2 In above node logs it showed exactly how the MID got selected, which is to say that it ended up with one MID after filtering for capabilities.We looked at the capabilities for both MID MID2 and MID1 and saw that MID2 had specifically POWERSHELL as a capability, while MID1 only had ALL as a relevant capability.Looking into our selection logic a bit more, we see that it don't match on ALL if we can match on a specific capability. Now that we identified why another MID server is selected instead of Default MID server, the solution is as follows: Remove the POWERSHELL capability from MID2 and found that MID1 got selected on the next run.Note that the Default MID only applies if there's no MIDs that match the criteria, but that's unlikely if every MID has ALL as a capability. Note: It is always advised that the customer set the MID capabilities with this information in mind.