Troubleshooting RCA issuesRestricted caller access (RCA) defines cross-scope access to an application and application resource, to set whether other applications can access data in another application. Useful community posts: https://community.servicenow.com/community?id=community_blog&sys_id=ce28d5b8db690c5c5129a851ca961999https://community.servicenow.com/community?id=community_question&sys_id=cbd8b9badbb9570058dcf4621f961982 Product doc: https://docs.servicenow.com/bundle/quebec-application-development/page/build/applications/concept/restricted-caller-access-privilege.html Examples of RCA errors: Read operation on table 'sn_hr_core_profile' from scope 'Global' was denied because the source could not be found. Please contact the application admin.Read operation on table 'sn_hr_core_profile' from scope 'Global' was denied. The application 'Global' must declare a cross scope access privilege. Please contact the application admin to update their access requests. Source descriptor is empty while recording access for table sn_hr_core_profile: no thrown error Some troubleshooting tips: OOB the necessary allowed RCA records are included.RCA issues on customer side are usually due to custom code (e.g. Creating/cloning an OOB widget might create a new RCA record in requested state. Updating a script include will automatically invalidates an existing allowed RCA records). Note: Customer are advised to perform RCA testing for any custom/customized widget in UAT before going to PROD.If gliderecord.get(<some valid sys_id>) returns false, it’s possible due to RCA issue (should be unrelated to ACL since glideRecordSecure is not used)It’s an obvious RCA issue if you see errors like “The application 'Human Resources: Service Portal' must declare a cross scope access privilege”. Some other time, RCA issue might not be as obvious (doesn’t show the cross scope access privilege error on the page) until you debug further. But in general if there’s any access issue, it’s a good practice to check the system log and check the list of RCA records to see if we need to allow any of the invalidated or requested ones.If the “Source” of the RCA is a customer-created record, it is the customer’s responsibility to update their RCAs (i.e. not a ServiceNow bug). If the “Source” of the RCA is an OOB, not-modified record, it may be a ServiceNow bug. Try to reproduce the issue on an OOB instance to see if the “Requested” RCA will be created.