Hi Y’all.
Nice to have a forum here just for us! 
I just wanted to give an update of what we are seeing on this issue of scheduled scans.
A couple of weeks ago we moved our clients into a fresh copy of the default policy, as recommended by support.
It appears that the scheduled scans are now working as designed and displayed in the portal for each device.
We have not moved them back into the default policy yet, but will do so as time allows.
It looks very promising.
I do see devices that were off during the scheduled scan time get turned on and then run the scan and update the portal. They would also auto-acknowledge the alert in the portal.
The policy move seems to have fixed the issue.
Going to move some clients back to the originating policy and leave them for another week, to see what happens.
This is good news! If I understand correctly, I need to create a new copy of the policy the device is using and move the device to it. Correct? Does it matter if I copy an existing policy or do I have to create a new one?
We just copied the policy that the client was already using. That way we didn’t need to worry about adding any extra configurations to the “new” policy. It would appear that the existing policy is not actually bad. It is just not being fully enforced. And moving from one policy to another, it corrects the “Connection” so the the whole policy is enforced. (That is just my speculation)
I believe that once you move the computers from the old policy to the copy, you can move them back fairly soon and you can delete the copy. We waited a couple of weeks before moving back, just in case.
For some unknown reason, some policies degrade and cause the devices assigned to them to not behave as expected.
The recommendation is to create a new policy and re-assign the devices.
Oh, sorry. We are creating copies of the old policies. Not creating new ones. You may be right. At this point, the “Copy” fixed the issue, but that could change tomorrow. 
Unfortunately that didn’t seem to make portal scans work for my PC.
I did get another updated from support saying they are still investigating but there are no additional updates at this time.
Hmm, I just realized that we have just been testing the scheduled scans. We will test a portal scan too.
Nice to see you guys here ! I’ve had the same message from support, that the problem isn’t fixed yet. Creating copy policies seems to have worked for a while, but I’m not convinced that it’s a long-term solution. Seems to fail again after a while.
Well it has been an ongoing issue for ages. January 2024 was the start of one report on the former community, but suspect there were several before that. My current case started at the begining of December 2024.
Hopefully they are now really investigating it.
Yeah, i think the issue may go back quite a few years. I have discovered that the scan command from the portal does appear to work, at least during testing.
But we noticed that the scans started from the portal do not show up in the history on the end point. Also, some computers are showing in the portal as having their last scan at around 1:00 am to 1:30am, which is correct. But some other computers in the same policy are showing 6:50am. Maybe it took that long to finish the scan?
It seems that portal-generated scans are silent, and therefore do not appear anywhere on the device logs. That being said, I’ve just been advised by support that they think the general problem of Policy and ad-hoc (portal) scans not running has been resolved, so I’m hopeful. The number of alerts has certainly plummeted, so fingers crossed !
That is good news about the possibility that the issue has been corrected. It is not a good sign that the portal generated scans are not logged or documented. That’s kind of dumb.
I got an email yesterday saying:
The reported issue is still being investigated by our development team, and there are no additional updates at this time.
But fingers crossed it comes in the next update.
Ok, so it sounds like the support team is not on the same page. We need George.