--- title: "Wake-up calls and tasks" slug: "wake-up-calls-and-tasks" tags: ["Agent", "Product Usage"] updated: 2026-08-26T12:53:43Z published: 2026-08-26T19:15:28Z canonical: "docs.trellix.com/wake-up-calls-and-tasks" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.trellix.com/llms.txt > Use this file to discover all available pages before exploring further. # Wake-up calls and tasks A wake-up call triggers an immediate agent-server communication rather than waiting for the current interval to elapse. ###### ### Note Use **System Tree** actions to wake up Trellix Agent. There are two ways to issue a wake-up call: - **Manually from the server** — The most common approach and requires an open wake-up communication port. - **On a schedule set by the administrator** — Useful when a policy requires manual agent-server communication. The administrator can create and deploy a wake-up *task*, which wakes up Trellix Agent and initiates agent-server communication. Some reasons for issuing a wake-up call are: - You make a policy change that you want to enforce immediately, without waiting for the scheduled ASCI. - (ePO - On-prem) You created a task that you want to run immediately. The **Run Task Now** option creates a task, then assigns it to specified client systems and sends wake-up calls. - A query generated a report indicating that a client is out of compliance, and you want to test its status as part of a troubleshooting procedure. (ePO - On-prem) If you converted a particular Trellix Agent to a **SuperAgent**, it can issue wake-up calls to designated network broadcast segments. **SuperAgent** distributes the bandwidth impact of the wake-up call. :