Domain Separation: MID Server ECC Queue output remains State = ReadyIssue <!-- /*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: ; } } ECC Queue [ecc_queue] Output record State stays at "Ready", and "Processed" timestamp remains empty. However, other ecc_queue similar output records perhaps with the same topic, mid server, and format in the source are quickly getting processed. The instance is a MSP/Domain Separated one. 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 MSP Domain Separation enabled instance. Cause<!-- /*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: ; } } Domain separation is the key to the issue. The ECC Queue has a Domain field, and the usual rules about record visibility applies. If the MID Server can't see the record, then it cannot pick up that job. For example, the ecc_queue topic was "RESTProbe" but it could have been any topic. The MID Server login user's sys_domain was not in same sys_domain as the RESTProbe ECC output record. Other ecc_queue output records with same topic, same mid server, same source, similar syntax in the name field, are getting processed as expected. The sys_domain field value was "global" for these ecc_queue output records. MIDSERVER sys_user record: ... <sys_domain>2b2b2b2b2b2b2b2b2b2b2b2b2b2b2b2b</sys_domain> <sys_domain_path>!!!/!!#/!!!/!!!/</sys_domain_path> ... <user_name>MIDSERVERUSER</user_name> Domain separated RESTProbe ecc_queue output record: <agent>mid.server.MIDSERVER</agent> <name>post</name> <processed/> <queue>output</queue> <source>http://source/subsource/actionname/action/</source> <state>ready</state> <sys_created_by>ADMIN</sys_created_by> <sys_created_on>2019-05-08 16:54:00</sys_created_on> <sys_domain>1a1a1a1a1a1a1a1a1a1a1a1a1a1a1a1a</sys_domain> <sys_domain_path>!!!/!!#/!!!/</sys_domain_path> <topic>RESTProbe</topic> Resolution<!-- /*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: ; } } The MID Server records will get created in the same Domain as the login user set for that MID Server. MID Servers will tend to either be in the Global domain, so that they can run jobs from, and see ecc_queue output records from any domain.or a leaf domain (the end of a branch, with no child domains), so that when the input ecc_queue record retuns to the instance, the transaction to process it will be in the same domain as the output was. The jobs sensor will see the domain-specific data relevant to the job. Using a MID Server in an intermediate domain often causes problems, and is not supported by some applications/integrations. Changing the domain of a MID Server to match the job is problematic, because as well as changing the domain of the login user, all the MID Server's records will also need their domain changing to match. That is also likely to affect other features and integrations also using that MID Server. So the solution is usually to ensure that the job that creates the e.g. RESTProbe is running as the correct domain to match the MID Server, so creates the ecc_queue output record in the domain the MID Server can see.