Run a Diagnostic Playbook

Overview

Diagnostic playbooks are pre-built scripts that collect live data from a device through the Plenix Agent — disk usage, running services, recent errors, pending updates, network connectivity, printer queues, and top resource consumers. They're read-only: nothing on the device is changed, only inspected.

Before you begin

• The device must have the Plenix Agent installed and online — diagnostics cannot run against agentless or offline devices
• The ticket must have a device linked to it

Running a playbook

1. Open the ticket and look at the Linked Device panel in the right-hand sidebar — it shows the device name and a green/grey dot for online/offline status.

2. Under Run Diagnostics, click any of the 7 playbook buttons:

   Playbook	What it collects
   Disk Usage	Drive space summary and the 10 largest folders on C:\
   Service Status	Automatic-start services that have stopped, plus app crashes in the last 24h
   Event Log Errors	System and Application error events from the last 24h
   Pending Updates	Pending reboot flags and count of pending Windows updates
   Network Connectivity	Default gateway ping, DNS resolution, and public latency
   Printer Queue	Status and queued job count for every printer on the device
   Resource Consumers	Top 10 processes by CPU and by memory

3. The button shows a spinner while the playbook runs. Within a few seconds you'll see a result message below the buttons.

Reading the result

• "Completed — view run in Autonomy" — the playbook ran immediately and succeeded (this is the default for all 7 built-ins, since they're risk-tier read)
• "Queued for approval — check Autonomy Approvals" — an admin has changed this playbook's policy mode to Suggest/Approve; see Approve or Reject Pending Actions
• "Failed to start — check Autonomy Approvals" — the request was rejected (e.g. a rate cap was hit) or the agent didn't respond

Viewing full output

Every playbook run is recorded as an Action Run with a full transcript of each step and its output. If the run needed approval, open Autonomy → Approvals and click View intended action to see it (also visible there after approval/rejection). Diagnostic output that ran via AI Triage also appears directly in the ticket's [AI Triage] internal note.

Where to go next

• Use AI Ticket Triage
• Configure Autonomy Policies
• Approve or Reject Pending Actions