LSAgent scans are occurring outside of Scan Schedule

[StorageMgr]

We have roughly 1300 LsAgents deployed, mostly on Laptops operating off-WAN, on public and private networks, using Citrix. Despite all but 50 devices currently being configured with the "One Time" Scan Schedule and the "LsAgent only" option, we receive multiple scans each day from these devices. These are all Windows-based devices, and should a staff member decide to work in the office, I have the scanning target option for our company subnets configured with "Scan New Windows Only". When I look at the Scan time for a device, the last scan time matches the "LsAgent directly via scan server" scan time. The unscheduled LsAgent scans are occurring when devices are connected to our LAN/WAN, not when they are off-WAN.

What am I missing? How might these LsAgent scans be occurring with the configuration I have described? My one thought is that the configuration changes, including the schedule, are not getting pushed to the LsAgents, so I'll be checking that shortly. But before the change to "One Time" they were initally configured with "none selected," which is my understanding defaults to once a day.

[StorageMgr]

Since most of our LsAgents reside on laptops that do not have access to our Lansweeper server, we use the LsAgent Relay service. By default, it has a 60 Minute "Sync Interval." Looking at the LsAgentlog.txt file on my workstation for some reason this is treated as a schedule to perform a scan. The cycle below repeats every hour, and the LsAgent directly via scan server time updates every hour, along with the Last scan attempt and Last successful scan date/time entries.

025-11-24 12:38:14,136 [5] INFO Waiting 60 minutes until schedule check, next scheduled iteration: November 24, 2025 13:38
2025-11-24 13:38:14,179 [5] INFO Reading ini file.
2025-11-24 13:38:14,181 [5] INFO Loading LS Agent Configuration File.
2025-11-24 13:38:14,184 [5] INFO Getting asset id
2025-11-24 13:38:14,185 [5] INFO Existing asset id found: b466fb81-0466-43bd-a721
2025-11-24 13:38:14,188 [5] INFO Creating communication channel
2025-11-24 13:38:14,190 [5] INFO CreateReachableEndPoint for b466fb81-0466-43bd
2025-11-24 13:38:14,247 [5] INFO Creating InternalCommunicationSender to URL https://lansweeperSrv:9524/lsagent
2025-11-24 13:38:14,248 [5] INFO Getting asset status from cache
2025-11-24 13:38:14,251 [5] INFO Asset is enabled
2025-11-24 13:38:14,253 [5] INFO Retrieving configuration
2025-11-24 13:38:14,255 [5] INFO Getting configuration from cache
2025-11-24 13:38:14,258 [5] INFO Updating local config
2025-11-24 13:38:14,263 [5] INFO Checking version. Latest Version: 12.2.0.1. Current Version: 12.2.0.1
2025-11-24 13:38:14,264 [5] INFO Schedule triggered
2025-11-24 13:38:14,266 [5] INFO Starting scan
2025-11-24 13:38:15,553 [5] INFO Scanning computer...
2025-11-24 13:38:15,569 [5] INFO Starting MsStore Apps scan.
2025-11-24 13:38:16,282 [5] INFO 2 MsStore Apps found during scanning.
2025-11-24 13:38:16,284 [5] INFO Finished MsStore Apps scan.
2025-11-24 13:39:35,549 [5] INFO Computer scan completed
2025-11-24 13:39:35,551 [5] INFO Serializing ScanResult
2025-11-24 13:39:35,590 [5] INFO Compressing scan file
2025-11-24 13:39:35,600 [5] INFO Sending scan
2025-11-24 13:39:35,672 [5] INFO Scan has been sent
2025-11-24 13:39:35,673 [5] INFO Saving ini settings
2025-11-24 13:39:35,678 [5] INFO Creating ini backup.
2025-11-24 13:39:35,680 [5] INFO Waiting 60 minutes until schedule check, next scheduled iteration: November 24, 2025 14:39

[StorageMgr]

Using Gemini I found "Lansweeper's Active Directory (AD) scans can indeed cause LsAgent scans to run." I want to confirm this is accurate and not some hallucination. 

If this is accurate, how frequently would I expect LsAgent scans with an AD Directory Domain scan with options of Check interval of 15m, Min Time of 20 hrs and Max Time of 2 days.