Common sidebar issues and workaroundsThis article describes the common sidebar issues and workarounds. Users experience slow responses or session timeout when searching chat participants. Symptom: When trying to search chat participants, sometimes users could experience long time to see the search results loaded or even session timeout. Root Cause: The root cause of this issue is every time when users provide a search term for participants, server side runs an expensive query to check if those users have permission to the record. If the number of matched users are large, it could be slow to return results or even trigger graphql execution timeout.Workaround: Currently there isn't a good workaround. Customers can try following this KB1282006 (must be logged into NowSupport to view) to create search type member query rule to filter down the potential chat participant candidates. With a smaller size of candidate users, customers may get some degree of relief. Unable to add "Discuss" button in workspaces Symptom: Customers may face some issues when trying to add "Discuss" button in workspaces.Workaround: Please refer to KB1213249. Disable "Discuss" button in classic UI(UI16) Symptom: Some customers ask to disable "Discuss" button in classic UI, but wants the button to work in workspace still.Workaround: Override the Discuss button by creating a UI Macro called "collab_chat_form_button" with an empty jelly tag in the xml field. AI search not work for previous messages after upgrade store app in Utah release Symptom: Upgrade store app version to 2.1.5 on Utah release and then do AI search on the previous chat message, the search result returns empty. Root Cause: A new field "deleted" is added to chat message table to support delete message function, and AI search source for the chat message table has a new condition deleted=false. AI search does not work well with this condition change. Workaround: Index the chat message table manually. Seeing cross scope access error when trying to start the discussion on a HR related record Symptom: On either workspace or UI16, open a HR record. Try start a discussion with the record. User will not see the Sidebar chat window opened and see an error message saying something like “Read operation for table XXX from scope Omni-Experience Standard Feature Set was denied”. Symptom: On either workspace or UI16, open a record that Sidebar supported. Try start a discussion with the record. User will not see the Sidebar chat window opened and see an error message saying something like “Read operation for table XXX from scope Omni-Experience Standard Feature Set was denied”. Resolution: User need to create the cross-scope access privilege for the Sidebar app. To achieve this, user need to take the following steps(use the table sn_hr_core_case_workforce_admin in the HR core scope as an example): Have a user with the admin/maint roleIn the “Omni-Experience Standard Feature Set” scope, create a new Cross scope privilege record for the corresponding table. Switch to table’s scope(in this case, HR core scope), create two new Restricted Caller Access Privilege record for the two Sidebar ACLs. The record should be like below: