The Script Results section in Trio provides a centralized, real-time interface to monitor the outcome of script executions across enrolled devices. After scripts are dispatched—whether manually, on schedule, or via automation triggers—their status, output, and execution metadata are captured and displayed in this view.
This capability is critical for IT administrators responsible for verifying task completion, diagnosing script failures, validating configurations, and performing audit reviews. It enables granular visibility into device-level execution, including exit codes, logs, runtime errors, and script-specific output.
Prerequisites
Only users with permissions to execute or manage scripts—such as Super Admin, IT Admin, or custom roles with “Script Execution Log Access” enabled—can view this section.
For script results to be generated, the following conditions must be met:
The target device must have the Trio agent installed and active.
A script must have been assigned and executed (either completed or failed).
Devices must be capable of communicating with the server at the time of result transmission.
Scripts must not have been interrupted by network errors, timeouts, or manual cancellations before logging.
Access Path
Fleet → Scriptor → Results
Overview of the Results Interface
When scripts are run, Trio collects and presents result records in a structured table. The top of the view includes a search bar and multi-dimensional filters to refine visibility based on:
Status – Filter by outcome (e.g., Success, Timeout, Error)
OS/Environment – Windows (CMD/PowerShell) or macOS (bash/zsh)
Exit Code – Custom or standard exit codes (e.g., 0 for success)
Device – Device name that ran the script
Finished On – Timestamp for script completion
Each result entry includes the following:
Script Name – The name as defined during creation
OS (Env) – The operating system and execution environment (e.g., PowerShell)
Device – The specific endpoint that executed the script
Exit Code – Numeric output indicating execution result
Status – Success, Timeout, or Error
Finished On – Timestamp of completion
Viewing Script Result Details
Clicking on any result row expands the Script Result Details view. This modal contains a comprehensive execution breakdown, including:
Device – The full name of the endpoint
Group Name – Organizational group where the device belongs
Run As – Execution privileges (System/Root)
Exit Code – The returned exit value (e.g., 1 = general error, 0 = success)
Server and Agent Time Sync – Useful for timing discrepancies
Started / Finished Timestamps – Exact start and stop times
Files – If any were attached or downloaded
Raw Script – The full script content as executed on the device
Script Log Output – Standard output or logs returned by the agent, including runtime messages, error traces, or echo values
Exporting Script Results
In the result detail view, an Export button is available. This allows administrators to download the result details (typically in JSON or CSV) for compliance, offline review, or ticket escalation.
This export includes all execution context: device metadata, logs, script content, and timestamps. It's especially valuable when investigating system misconfigurations or failed deployments.
System Behavior Notes
Timeouts occur when a script exceeds its defined runtime limit. These are marked clearly in red with a “Timeout” status and exit code
1.Errors may result from syntax issues, invalid paths, permission problems, or missing dependencies. These return status “Error” and exit code
1(unless overridden by the script).Success is indicated by the exit code
0and green “Success” labels.Agent-side delays or failures in result transmission may cause missing or partial logs.
Device offline at finish time? If the script executes but the result fails to sync, it may not appear. Ensure reliable network connectivity.
Troubleshooting
Missing Results? Confirm the script was properly assigned, and the device was online during and after execution.
Unexpected exit code? Refer to your script’s logic and ensure return values are correctly defined.
Log output missing? Ensure the script writes output to STDOUT or STDERR, which Trio captures.
Status shows Timeout, but finished? This may indicate a mismatch between the timeout configuration and the actual execution time. Review the “Timeout” setting under the script definition.