Service Exchange (Bridge) Remote Provider Sync (RPS) attachments not syncing to provider taskIssue <!-- /*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: ; } } When a consumer instance sends attachments via Service Exchange (Bridge) Remote Provider Sync (RPS), the attachments arrive on the provider instance and appear in the 'sys_attachment' table but are never transferred to the provider task. Attachment sync fails silently or with a misleading error, while work notes and record data continue to sync as expected. Symptoms<!-- /*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: ; } } - Attachments added on the consumer side do not appear on the corresponding provider task- Attachments are visible in the 'sys_attachment' table on the provider instance but remain associated with the 'ih_sync_correlation' table in a Pending state- The 'attachComplete' API returns the following error: 'The inputs provided to the action: Move Attachments within application scope: global are incorrect, please refer to the definition.' - Service Bridge logs show: 'Transport.checkForMissingAttachments - FAILED: [..., "failedToArrive":true]' 'Attachment '<filename>' for table: sn_sb_con_provider_task, and record: <sys_id> failed to arrive when expected from other instance (connection is slow, down, or attachment has unsupported extension)' - The "Service Bridge RPS Inbound Flow" shows no flow context executions for attachment processing over an extended period- Impersonating the RPS run-as service account and executing the 'global.move_attachments' action via script reproduces the same "incorrect inputs" error- The same action executes successfully when run as a maintenance ('maint') or global admin user- Work notes and additional comments continue to sync without issue — only attachments are affected- The issue affects all consumers onboarded to the provider, not a single connection Facts<!-- /*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: ; } } - Service Exchange (Bridge) is deployed in a domain-separated environment- The instance uses Remote Provider Sync (RPS) for attachment processing- The 'sys_hub_action_type_definition' table contains a duplicate entry for the 'Move Attachments' action scoped to a non-global domain, rather than only in the global domain where the out-of-box (OOB) system-level action resides- The duplicate action record has no inputs defined, causing FlowAPI to fail when it resolves this action instead of the OOB version- The duplicate action was not visible through the standard Action Designer UI, because it is flagged as a system-level action; it is only reachable via direct URL navigation to 'sys_hub_action_type_definition'- Instance authentication: OAuth (Open Authorization) between consumer and provider instances; RPS run-as service accounts ('sb_user.*') are system-generated during SB registration and are scoped to the domain of the connection 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: ; } } All currently supported releases where Service Exchange (Bridge) RPS is used in domain-separated instances. 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: ; } } A duplicate 'Move Attachments' action type definition record ('sys_hub_action_type_definition') exists in a non-global domain on the provider instance. This duplicate record has no input definitions.When the 'attachComplete' API triggers the 'global.move_attachments' action via FlowAPI, the platform resolves the domain-scoped duplicate instead of the OOB system-level action in the global domain.Because the duplicate record has no inputs, FlowAPI throws the error 'The inputs provided to the action: Move Attachments within application scope: global are incorrect, please refer to the definition', and attachment processing halts. Record and comment sync are unaffected because they do not use this action.The duplicate records are typically created when a script performing a bulk update runs against action type definition records using a standard 'update()' call instead of 'updateNoDomain()', inadvertently copying system-level actions into a child domain. This can occur during instance cloning, a fix script, or a customization that was not domain-aware. 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 steps below remove the duplicate action type definition record that is causing the override. This restores attachment sync to expected behavior by allowing FlowAPI to resolve the correct OOB system-level action. Before proceeding, confirm that a duplicate 'Move Attachments' record exists in a non-global domain: 1. Navigate to the following URL on your ServiceNow instance, replacing '<instance-name>' with your instance name: 'https://<instance-name>/sys_hub_action_type_definition_list.do?sysparm_query=nameLIKEMove+Attachments' 2. Review the results. Confirm that two records named 'Move Attachments' are present — one in the global domain (the OOB system-level action) and one in a non-global domain with no inputs defined. Note: The duplicate record may not be visible in the Action Designer UI because it is flagged as a system-level action. Use the direct list URL above to locate it. 3. Open the duplicate record scoped to the non-global domain (the record without inputs defined). 4. Clear the **Sys Overrides** field on the duplicate record if it is populated. 5. Delete the duplicate record, or use a background script to remove it if the record cannot be deleted through the UI due to domain restrictions. Use the following script template as a guide: var gr = new GlideRecord('sys_hub_action_type_definition'); gr.addQuery('name', 'Move Attachments'); gr.addQuery('sys_domain', '!=', 'global'); gr.query(); while (gr.next()) { gs.info('Found duplicate: ' + gr.sys_id + ' in domain: ' + gr.sys_domain); // Uncomment the line below only after confirming the record to delete // gr.deleteRecord(); } Run the script in read-only mode first to confirm the record before deleting. 6. After removing the duplicate record, test attachment sync by adding an attachment on the consumer instance and verifying that it appears on the provider task. 7. Optionally, review whether other system-level actions have been duplicated into non-global domains using the following query:https://<instance-name>/sys_hub_action_type_definition_list.do?sysparm_query=system_level=true^sys_domain!=global Remove any additional duplicates that do not belong in non-global domains, following the same process above.