After Delivery Controller changes (example: farm migration), Citrix Workspace App may resume from hibernation with stale cache and fail to launch resources until a manual refresh is done. Has anyone found a better or more automated way to handle this (for example auto-refresh or self-healing behavior), without requiring user action?

it's linked to the name you put in the Delivery Controllers group when configured in Storefront. keep the same name, you won't face the issue (it's just a string, no UUID or whatever).

Unfortunately, it didn’t work as expected for some users with an outdated cache in CWA (for example, when the OS was started from hibernation). No issues for web browser users.

Using that example: when the user clicks on an icon in CWA, it asks for "CVAD.Your Application". So if you group the new DDCs under another name, CWA will still try to ask for "CVAD.Your Application" until cache is refreshed.

Yes, exactly — the StoreFront Delivery Controller group name was kept unchanged. Despite that, some users still experienced the issue because Citrix Workspace app continued to use outdated cache data (e.g., on devices resumed from hibernation), so it was still using the previous state instead of the updated configuration. Source of issue - lack of cach refresh. How to avoid? Any way to „force” refresh automatically instead of „manually” by user?

I am surprised it changed. You may try this: https://support.citrix.com/external/article/CTX200337/driving-the-citrix-receiver-selfservice.html

I have plenty of issues with CWA cache, the web browser is way more reliable ... They should just do something with no cache or something smarter.

I can see space for improvment from Citrix in this topic 😉