I have experienced this in the past, usually around the same time of the
year, deployment time of course. Support corrects it by restarting the
VPP License Monitor, my instance is cloud hosted so they do it from
their end. I'm not sure what the proce...