Skip to main content

Actions and runs

Running an Action on endpoints creates a run. A run records every targeted endpoint, sends the Action out in waves, and keeps the outcome of each endpoint, including endpoints that were offline and never got it.

Plan availability

Running Actions is included on the Professional plan and above. If your plan doesn't include it, the app names the plan that does: organisation admins get Request upgrade and See plans, and other members are asked to talk to an admin. In your personal workspace, it asks you to create or switch to an organisation. Past runs stay readable on every plan. If response actions are temporarily turned off for maintenance, run and approve controls are disabled with "Response actions are temporarily turned off." Runs you've already started stay visible.

Start a run​

WhereHow
Content library › ActionsClick Run on an Action, or on its page.
An endpoint's pageChoose Respond and an Action under Saved Actions. The run targets that endpoint only.
ScoutScout can propose a run. You approve it in the chat, the hunt, or the Inbox. See Scout proposals.

In the Run dialog:

  1. Choose the fleet and the targets: specific Endpoints, endpoints carrying a Tag, or the Whole fleet. For tags, the dialog shows how many endpoints match and how many are offline.
  2. Fill in the parameters, or pick a preset.
  3. Choose the rollout (below) and how long the run waits for offline endpoints, 1 to 24 hours.
  4. Give a reason. It goes into the audit log.
  5. Click Run. If the Action needs approval, the run waits in Needs approval.

Rollouts​

A run reaches endpoints in waves. Between waves it checks a failure gate, and it pauses if too many endpoints failed.

RolloutWavesStops ifWho can choose it
Canary first1% of targets (at least one), then waits for a person to click Continue, then 2,000 every 2 minutesMore than 5% failAnyone who can run the Action
Standard2,000 every 2 minutesMore than 5% failAnyone who can run the Action
Urgent10,000 every 30 secondsMore than 10% failOrganization admins, with a reason

Small runs fit in one wave, so a run on a single endpoint goes out immediately.

Follow runs in Action runs​

The Action runs page lists runs across all Actions: those running, those waiting for approval, and recent ones. Filter by Needs approval, Running or Finished. Its breadcrumb reads Explorer › Investigate › Endpoints › Action runs.

To open it:

  • In the classic navigation, click Activity › Action runs.
  • In the new navigation, open Investigate › Endpoints › Action runs. You can also follow any link to a run, such as a run on an Action's page or an endpoint's outcome.
Rolling out

The new navigation is rolling out and may not be enabled for your organization yet.

A run's page shows:

  • progress by state across all targets;
  • each wave and the failure gate;
  • one row per endpoint with its state, exit code, duration and the first 2 KB of output. Click Show full output for the rest.

Controls depend on the run's state and your access: Approve, Reject, Continue (after a canary), Pause, Resume, Stop, Retry failed and Retry expired. A retry starts a new run for just those endpoints, linked to the original.

Endpoint states​

StateMeaning
WaitingNot sent yet; its wave hasn't started.
SentSent; the endpoint hasn't checked in.
RunningThe endpoint is running it.
SucceededFinished with exit code 0.
FailedFinished with an error. The output says why.
Timed outRan past the script's timeout and was stopped.
DeniedThe endpoint refused it, for example because safe mode is on or a check failed. The reason is shown.
ExpiredThe endpoint didn't check in before the run expired.

A run ends as Completed, Partial (some endpoints didn't succeed) or Timed out.

On an endpoint​

An endpoint's Response history tab lists every Action outcome on that machine, above its response history. Each outcome links to its run. An endpoint that is isolated right now carries an Isolated badge in its header.

Scout proposals​

Scout can look up Actions, check a run's progress, and propose a run. Scout never approves anything:

  • A proposal is a run that waits for a person's approval, shown as a card in the chat or hunt, or sent to your Inbox when Scout is working on its own.
  • Scout can't propose an Urgent rollout.
  • A proposal for more than 25 endpoints, or for a tag, always starts with a canary that a person must continue.

Output and retention​

The first 2 KB of each endpoint's output is kept with the run. The full output, up to 64 KB per stream, is stored in your organization's storage destination, or in Huntbase storage if you haven't set one.

Next steps​