This page answers common questions about how SASE schedules and runs terminal protection scan tasks, including how the system handles task priority, offline devices, and task conflicts.
How does the system handle multiple scheduled scan tasks from the same user?
Tasks run in priority order. Higher-priority tasks are delivered and run first. If two tasks have the same priority, the system runs them in reverse chronological order — the most recently created task runs first.
Does the system scan a device when the user is offline?
No. When a scheduled scan task starts, the system tries to detect all user devices within the effective range. If a device is not detected, the system keeps retrying for up to 45 minutes. If the user remains offline for the entire task execution period, the system delivers and runs the scan task when the user comes online.
Because the system waits for each user to come online, different users may end up on different scan cycles even if they share the same scheduled task.
For example, suppose you create a scheduled scan task that runs every 3 days starting January 1. User A is online every day from January 1, and User B is online every day from January 2. Because User B missed the first execution window, the system runs the task for User B on a different cycle than for User A, as shown below.

What happens when both an immediate scan task and a scheduled scan task are due on the same day?
The system runs only one scan task per user per day. If a scheduled scan task has already run for a user on a given day, the system skips any immediate scan task for that user on that day.
Why does an immediate scan task require an end time?
The end time is the cutoff for picking up offline devices. When you create an immediate scan task, the system scans all online devices within the effective range right away. If a device comes online before the end time, the system delivers and runs the scan task for that device. Once the end time passes, any device that was offline during the entire task period is not scanned.
Devices that were already online when the task started are not scanned again before the end time expires.