After an upgrade one of the fix versions (i.e., Yokohama Patch 5), Lists in Service Operations Workspace are not automatically refreshingDescriptionBuild name: YokohamaDescription: After an upgrade, one of the fix versions (i.e., Yokohama Patch 5), Lists in Service Operations Workspace are not automatically refreshing Although I followed the steps/guidance in KB2004278 internal article, the issue still persists.Steps to Reproduce In Yokohama Patch 5 instance with the SOW Version 6.1.0 plugin as well as the following property set to true ; glide.lists.live_list_enabled1. Hop in your instance,2. Navigate to 'Service operations workspace' from workspaces 3. Go to incidents -> All -> click (+) or new to create a new incident record4. The newly created incident record doesn't show up to the list unless you refresh the page manually. Expected behaviour : The newly created incident record should be automatically appeared.Actual behaviour : The newly created incident record doesn't show up to the list in 'sow list prb1.png' screenshotWorkaroundPlease check out KB2004278.The issue is seen on the new "List Bundle SNC" page introduced starting with SOW v6.1 following workaround can be used where list page would simply work as previous sow version prior to v6.1:- Deactivating the new "List Bundle SNC" variant. 1. Go to the UI Builder and open "Service Operation Workspace" experience. 2. In the list of pages, search for "List Bundle SNC". This variant should come up under List page with OOTB order value 90. 3. Go to the settings of the above variant page, uncheck Active field and save the record to deactivate the variant. Now, go back to the SOW list page and refresh the page once so the changes take effect.Note: -> By deactivating the the new variant, customer will lose the new functionalities like the fuzzyCount, row level actions (Copy URL, Copy sys_id) etc features that are available with "List Bundle SNC" page. For more info, check out the product doc: https://www.servicenow.com/docs/bundle/xanadu-it-service-management/page/product/service-operations-workspace/task/incident-list-page.html-> Marking the variant as inactive, also makes the underlying record treated as customized. Hence, when at later point in time when SOW is upgraded, customer will need to review the changes made to the underlying record and make sure it is not skipped on upgrade.The following record(s) will be marked as customzied with above change:- sys_ux_screen_e4d46ab3ebc412103890ddde235228a8Related Problem: PRB1919567