Hi @Gianluca7
That message usually means one component (or the whole landing page variant) on the workspace home page failed to render after the upgrade. Before repairing the plugin, I'd check these in order:
1. Upgrade skipped records
- Go to System Diagnostics > Upgrade History, open the Australia upgrade and filter Skipped Changes for "landing", "home", "sn_csm" / "sn_customerservice" and UX records (sys_ux_macroponent, sys_ux_page_registry, sys_ux_screen).
- If your landing page was customised earlier, the OOB Australia version gets skipped and your old page may reference components/data resources that changed. Review and merge, or revert to base system.
2. Landing page variant in UI Builder
- Open UI Builder > CSM/FSM Configurable Workspace > Landing page (Home).
- Check which variant is active for your users (audience, conditions, order). If a custom variant is active, temporarily deactivate it or test with the OOB variant to see if the error goes away.
- If the OOB variant works, create a fresh copy of the current OOB variant and reapply only the customisations you need.
3. Find the exact failing component
- Open the home page with the browser dev tools console open (F12) and look for red errors (component not found, data broker / script errors, 403 from ACLs).
- Also try with an admin user vs. an agent user. If it only fails for agents, it is likely a role/ACL on a data resource used by a widget.
4. Cache and Repair (last resort)
- Run cache.do and retest.
- Plugin Repair (App Manager > com.sn_customerservice > Quick Action > Repair) reloads the plugin's records. Try it on a sub-prod instance first, since it touches a lot of records, and re-check your customisations afterwards.
If you can share the console error or the name of the component showing the message, I can point to the exact fix.
If this helps, please mark it helpful or accept it as the solution so others can find it.
