Teams Calling Policies Rollout

I have been working on screen pops for inbound PSTN calls, specifically the "Open apps in browser for incoming PSTN calls" & "URL to open apps in browser for incoming PSTN calls" settings in Calling Policies.

Is there any documentation on how the whole policy application process works in Teams? It seems to be frustratingly inconsistent.

My experiences with updating the link used in calling policies with Windows Desktop clients:

1. During the first production rollout, it took days for some clients to pick up changes to the link. I am logging which pop screen is activated and saw that some picked up the change in a couple of hours, but a few here and there took a couple of days. One lone straggler never picked up the policy change even after having him restart the app, then logout out of Teams and restart. He finally picked up the change after I toggled a policy switch off and on saving twice in between. If picked up within a few minutes.
2. During testing this week, I changed the link in the calling policy, and it did not take effect even after 24 hours on the test clients. I again made a couple of tweaks to the policy, saved the policy, reversed the changes, saved again and within a few minutes, the policy applied to the test clients.
3. A day later, I opened a client using the same Teams account on a different computer and it still had the old policy. Several hours later, it was still using the old settings. Signing out/into teams and restarting the app did not trigger an update to policies.
4. About twelve hours ago, I made a policy change and so far, the client hasn't picked up the change. I shut down Teams, deleted the %appdata%\Teams folder and restarted the app. Interestingly, the %appdata%\Teams folder has not been recreated. Most apps recreate their folder right at launch, but it's been half an hour. The client is still using the old link setting.

Questions:

• Does anyone know if the 24 hours for policies to deploy is for the cloud to deploy, or for the client to check for updates?
• Does anyone know a reliable way to force a desktop client to refresh policies?
• Do certain policy changes trigger a more immediate rollout?

I seem to remember the Lync/Skype For Business clients having a scheduled update cycle for policies, but there were ways to force it to refresh by deleting files/folders, specific setting or running commands.

Testing aside, the fact that a policy change was never picked up in a week by at least one client, makes me wonder how many clients are running on outdated policies that we can't verify.