Fabric Lakehouse Shortcut does not refresh Variable Library target after active value set change

I am using a Microsoft Fabric Lakehouse shortcut whose target is configured through a Variable Library variable. The Variable Library contains separate value sets for Dev and Prod. In the Prod workspace, the Prod value set is active and contains the correct target Lakehouse/path.

However, the shortcut still points to the Dev target even though the Prod value set is active. When I open the shortcut configuration in the Lakehouse UI, edit the shortcut, and save it once without changing the actual value, the shortcut immediately resolves correctly to the Prod target.

This makes it look like the shortcut target is cached or materialized and is not automatically refreshed from the currently active Variable Library value set after switching value sets or after deployment. The Variable Library value itself seems to be correct, because manually editing and saving the shortcut fixes the issue without any real configuration change.

Expected behavior:
A Lakehouse shortcut that uses a Variable Library variable for its target should always resolve to the value from the currently active value set in the workspace. If the Prod value set is active, the shortcut should point to the Prod target.

Actual behavior:
The shortcut continues to point to the Dev target although the Prod value set is active. Only after manually editing and saving the shortcut does it resolve to the correct Prod target.

Impact:
This is risky for deployment scenarios because a Prod Lakehouse shortcut can still reference Dev data until somebody manually opens and saves the shortcut. This can lead to accidental use of data from the wrong environment.

Workaround:
Opening the shortcut configuration and saving it once seems to refresh the resolved target. However, this manual step is easy to miss and not suitable for reliable deployment or CI/CD processes.

Has anyone else seen this behavior with Lakehouse shortcuts and Variable Libraries? Is this a known limitation, a caching issue, or a product bug?