FetchPersonalizedConfigurationAsync cache

How does Milestone’s cache of a users’ personal ACM config work? Right now it seems sporadic… How long is the cache kept for? Is there any way to force it to fetch a new config before it expires? Etc.

I’m running into an issue with my plugin because if I change a users’ permission level in the access control https://speedtest.vet/ system https://vidmate.bid/ (ie what doors they are https://wordtopdf.ltd/ allowed to see/open), which doesn’t change the global ACM config (ie if I refresh the config from mgmt client it says no changes), that change is not visible in the smart client for the user until the cache is expired.

thankyou

Hi Rory

Cache expiration for credentials occurs either:

  • when ACSystem explicitly invalidates information triggering FireCredentialHoldersInvalidated() so it forces update in Smart Client.

  • communication fails between ACSystem and VMS, and once it is resumed, cache is explicitly refreshed

If you are not explicitly invalidating outdated configuration the second scenario could be the one that creates sporadic behaviour.

I hope the explanation helps with your issue.

Regards,

Jorge