The Queued Scripts view in Trio enables administrators to monitor all scripts that have been assigned but are still pending execution on targeted devices. This queue acts as a live staging area for scripts that have been triggered but haven't run yet due to conditions like device availability, schedule timing, or network readiness.
This functionality is essential for maintaining visibility and control over script deployment pipelines. Whether a script was triggered manually, scheduled, sent via webhook, or set to repeat, its status and progress can be tracked from this interface. From here, administrators can validate execution timing, investigate delays, or proactively stop scripts before they propagate further.
Prerequisites
Only users with script execution privileges can view and manage queued scripts. This typically includes roles such as Super Admin, IT Admin, or custom roles with access to the Scriptor module.
Devices listed in the queue must:
Have the Trio agent installed and actively reporting
Be part of a valid assignment (individual or group)
Match the script’s operating system and environment
Queued scripts will only execute when all execution conditions are met, such as agent connectivity, OS compatibility, and launch method readiness.
Access Path
Fleet → Scriptor → Queued
Step-by-Step Guide
Step 1: Navigate to the Queue
From the left sidebar, open the Scriptor module under the Fleet section. Then select the Queued tab at the top of the screen. If no scripts are currently pending, the interface will display a blank state message:
“No script queued. Queued scripts will appear here once they’re created.”
As soon as scripts are assigned and await execution, they populate this view automatically.
Step 2: Review Queued Scripts
Once populated, the Queued tab displays a structured table of all scripts currently in the execution queue. For each entry, the following data is visible:
Script Name – Title assigned at creation
OS (Env) – The target operating system and execution environment (e.g., macOS + Bash, Windows CMD, PowerShell)
Launch Method – Defines how the script was triggered (e.g., manually, on schedule, via webhook, or repeating)
Pending Devices – Number of devices yet to complete execution
Queued At – Timestamp of when the script entered the queue
Search and filter options allow administrators to sort the queue by name, operating system, or launch method. This becomes particularly useful in large environments where hundreds of scripts may be issued across varying device types and schedules.
Step 3: Stop a Queued Script
Administrators can halt queued scripts by clicking the Stop button in the rightmost column. Upon doing so, a confirmation modal appears with a warning:
“If you stop this script, all pending scripts will be removed.”
This action is irreversible. Clicking Stop cancels the deployment for all devices that have not yet executed the script. Devices that have already processed the script will not be affected, and their results will still appear under the Results tab.
This is particularly useful in scenarios where a misconfigured script was deployed, an error was identified post-deployment, or the script needs to be replaced with an updated version.
Step 4: View Script Execution Details
To inspect which devices are still pending and what status each holds, click into a script entry to open the Queued Detail page.
This detail view displays a device-level breakdown, including:
Device Name
Serial Number
Operating System
Assigned Group
Status (Pending, Receive, Failed)
Started Timestamp
Devices that have failed to execute the script are highlighted with a Failed status. Devices that have acknowledged the script but not completed it show Receive. Those awaiting agent response remain in Pending.
You can sort this list by name, status, group, or execution timestamp to troubleshoot efficiently.
System Behavior Notes
Queued scripts execute automatically when the assigned devices are online and meet all conditions.
Stopping a script removes it from the queue for all devices that haven’t run it yet.
Queued scripts remain visible until all associated devices either execute or are stopped.
Scripts assigned via webhook or schedule may appear in the queue even before device eligibility is triggered.
Devices that remain offline or unresponsive will indefinitely retain their queued status unless explicitly stopped.
Troubleshooting
Script stuck in queue?
Ensure the target device is online and connected to the Trio agent. If the device hasn’t synced recently, the script may remain pending indefinitely.
Script was queued but never executed?
Verify that the launch time wasn’t scheduled in the future and that the operating system matches the script’s configuration.
Accidentally queued the wrong script?
Use the Stop button immediately to remove it from all devices before execution begins. If any devices have already executed it, check the Results tab to assess outcomes.