Introduction
The Automations tab inside device details shows every automation that has run or is currently running on this device. Use it to check run history, inspect output from individual actions, filter by status, and trigger automations manually.
For building and managing automations themselves, see the Automations section of the docs.
Device Automation View
Each row in the table is a single automation run. The columns tell you:
Name — the automation that ran
Trigger event — what fired it (a schedule, a webhook, a device event like "Device created," or a manual run showing which technician triggered it)
Status — the outcome badge: Success, Failed, Warning, Running, Queued, or Canceled
Started / Ended — timestamps for the run
Duration — total time from start to finish
Runs are sorted by Started (newest first) by default. Click any column header to re-sort.
Filtering and Searching Runs
To find a specific run:
Type in the Search field to filter by automation name.
Use the Filter by status dropdown to narrow by outcome.
Available status filters:
Success — all actions completed without errors
Failed — one or more actions failed and the run stopped
Warning — the run completed but with at least one non-fatal issue
Running — currently in progress
Queued — waiting to execute
Canceled — the run was stopped before completing
You can use search and status filter together. They stack.
Inspecting a Run
Click the → arrow on any row to open the run detail panel.
The panel has 2 tabs.
Overview shows:
Run details — source (trigger), start/end times, total duration, and status
Workflow progress — each action in the automation listed in order, with its individual status badge, duration, and an expand arrow
History shows previous runs of the same automation on this device.
Viewing Action Output
Click the expand arrow on any action in the Workflow progress section to see its output.
The Output tab shows the raw log from that action — useful for debugging what actually happened on the device. The Input tab shows the parameters the action received.
A download icon next to the output lets you save the log.
ℹ️ NOTE: Actions with a "Skipped" status were not executed. This typically means a conditional step earlier in the workflow determined they weren't needed (for example, a "patching failed" alert action when patching succeeded).
Rerunning or Canceling an Automation
For a completed run, click Rerun in the run detail panel to re-trigger that automation immediately on this device. If the run failed, Rerun resumes from the failed step rather than starting over from the beginning. The new run appears at the top of the table.
ℹ️ NOTE: Rerunning triggers the automation immediately, regardless of its configured schedule or trigger.
For an active run, the panel shows Cancel run instead of Rerun. Click it to stop the automation mid-execution.
Triggering Automations Manually
To run an automation on demand without waiting for its trigger:
Click Actions in the top-right of the device header.
Select Run automation.
Choose the automation from the list and confirm.
You can also trigger automations by applying a tag to the device, if the automation is configured with a tag-based trigger. See Automations → Triggers for how to set that up.
💡 TIP: The Actions menu also includes Run saved script and Run new script for one-off script execution that doesn't need a full automation.
Exporting Run History
Click Export to CSV to download the current table view as a CSV file. The export respects any active filters — if you've filtered to "Failed" runs, only those export.
Selecting Multiple Runs
Check the box on any row to select it. The toolbar updates to show how many runs are selected and a Show only selected toggle appears at the bottom of the page. You can Rerun the selected automations or Export to CSV.
FAQ
How do I know which automations are configured to run on this device? The Automations tab shows run history and active runs, not a static assignment list. That's intentional — many things can cause an automation to run against a device: group changes, tags applied or removed, schedules, events like device creation, webhooks, or manual triggers. The run history here is your best view of what's actually fired and why (check the Trigger event column). To see automations linked at the group level, go to Group Settings → Linked Automations. For a full picture of how automations get assigned, see Automations → Getting Started.
Why does an automation show "Skipped" for some actions? Skipped means the action wasn't executed. Automations can include conditional branches — if an earlier action's result means a branch isn't needed, downstream actions in that branch are skipped. This is expected behavior, not an error.
An automation shows "Failed" but I can't tell which action caused it. Where do I look? Open the run detail panel by clicking the → arrow on the failed run. Expand each action in the Workflow progress section and check the Output tab for error messages. The failed action will have a red status indicator.
Can I cancel a run that's currently in progress? Yes. Open the run detail panel by clicking the → arrow on the running row, then click Cancel run in the top-right of the panel. Queued runs can be canceled the same way before they start executing.
Who can trigger automations manually on a device? Any technician with access to the device's group can use Actions → Run automation. If you don't see the option or it's grayed out, your permissions for this group may be restricted. See Workspace → Permissions for how access is configured.
The Rerun button isn't available. Why? Rerun appears in the run detail panel. If you're not seeing it, make sure you've opened a specific run by clicking the → arrow on a row, not just viewing the table. It's also possible your permissions don't allow triggering automations on this device.