REST API Access Policy does not work after cloneIssue <!-- /*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: ; } } After cloning from instance A to instance B, REST API Access Policy is not working in the cloned instance.To reproduce the issue:1. Assume there is an API access policy on incident table https://instancexxx.service-now.com/api/now/table/incident?sysparm_limit=1 and observe basic authentication failure.2. Observe the error response: {"error": {"message": "User Not Authenticated", "detail": "Required to provide Auth information"}, "status": "failure"}.3. Compare with the source instance, where the same credentials return a 200 OK response for basic authentication. 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: ; } } Yokohama 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: ; } } 1. The cloned authentication policy in the target instance contained invalid or misconfigured decision inputs, causing authentication failures for basic authentication requests.2. A specific decision input could referenced incorrectly in the policy's decision table, leading to authentication policy evaluation failures.3. The issue was exacerbated by cached policy configurations that were not properly updated after cloning, requiring cache flushing and policy recreation. Below warning may be observed in the node logs and can lead to an issue with cache: 2026-05-08 06:18:29 (464) API_INT-thread-1 SYSTEM txid=cf677c2c0ffc SSI_6aae0d3387021010d00b5773e8cb0bbe WARNING *** WARNING *** Error registering filter: global_a2310dd31baa52947d88c882604bcb95=true^NQglobal_108b5da787ea9e90c9902174dabb3569=true^global_6cf1c22787ee9e90c9902174dabb35ab=true^ORglobal_9693e9af872e9e90c9902174dabb3533=true^ORglobal_d67702e38722de90c9902174dabb35e9=true^ORglobal_052a53d43beeee10deb15c7aa5e45a84=true^ORglobal_32c088e4474a2a101510a5cc416d43e6=true^ORglobal_f814781c8728ba10c35fcb7f8bbb3566=true^ORglobal_f647c1c887df6210c9902174dabb358f=true^ORglobal_ac4ee47a3300c3142a1449a19e5c7bdf=true^EQ: Invalid field: [var__m_sys_decision_input_f0f0ea273b6e1e10deb15c7aa5e45a8b].global_f814781c8728ba10c35fcb7f8bbb3566, for term:global_f814781c8728ba10c35fcb7f8bbb3566=true 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: ; } } 1. Identify that the authentication policy may be misconfigured due to cloning issues.2. Flush the decision table cache for the affected policy using the script: var util=new AuthPolicyDecisionTableUtil();util.flushDecisionTableFromCache('sys_id of the authentiation policy');gs.info('flushed succcess'); 3. If the issue persists, deactivate the existing REST API authentication policy and recreate it with correct filters to ensure proper IP and role-based conditions are applied.4. Validate the resolution by retrying the basic authentication request in the source instance.