Luxor Documentation Hub Logo
Commander/Automation

Bulk Actions

Execute operations across multiple miners and track the full history of fleet actions

Overview

Managing miners one at a time doesn't scale. Bulk Actions let you execute operations - pool changes, power adjustments, firmware installs, reboots - across hundreds or thousands of miners in a single workflow. The Actions Log then gives you a complete audit trail of every operation that has run on your fleet, regardless of whether it was triggered manually, by an Automation Rule, or by Intelligent Miner. This is the page you check when you need to verify what happened, when, and to which machines.

Selecting Miners

To start a bulk action:

  1. Navigate to the Miners tab.
  2. Use checkboxes in the leftmost column to select the miners you want to act on. You can select individual miners or use the header checkbox to select all visible miners.
  3. As you select miners, the Bulk Actions button in the top-right corner updates to show the count of selected miners (e.g., "Bulk Actions (2)").
  4. Click the Bulk Actions button to open the Bulk Actions dialog.

You can apply filters before selecting miners to narrow down the set of machines for your bulk operation - for example, filter by firmware type and model first, then select all visible miners.

Bulk Actions

Building a Command Sequence

The Bulk Actions dialog allows you to build a sequence of one or more commands that will be executed on the selected miners. Each step in the sequence is a single action.

Available Actions

ActionDescription
Install LuxOSInstall LuxOS firmware on selected miners.
Update LuxOSInstall LuxOS firmware on selected miners. Supports both Stable and Preview release channels
SleepCurtail miners by putting them into a low-power sleep state
Wake UpResume mining on curtailed or sleeping miners
RebootRestart the selected miners
Change Power SettingsAdjust the power mode or power target
Change Pool SettingsUpdate the mining pool stratum URL, worker name, and password for selected miners
Change ATM SettingsEnable, disable, or configure Advanced Thermal Management settings

Multi-Step Sequences

You can chain multiple actions into a single command sequence. For example, you might change pool settings and then reboot the miners to ensure the new configuration takes effect. To add additional steps, click the + button or dropdown to add another action. Each step is numbered and can be reordered or removed using the drag handle and delete controls.

Once your command sequence is configured, click Continue to proceed to the Bulk Preview step.

Bulk Preview

Before executing any actions, Commander presents a preview of exactly what will happen. The Bulk Preview screen shows:

  • Bulk Actions Summary: A numbered list of the actions in your command sequence.
  • Total Miners: The number of miners that will be affected.
  • Batch Size: How many miners will be processed simultaneously (default: "All at once"). This can be configured to execute in smaller batches to reduce risk or network strain.
  • Delay: Time delay between batches (default: "No Delay").

Compatibility Check

Not all actions are compatible with all miners. For example, LuxOS-specific actions like ATM configuration cannot be applied to miners running stock or third-party firmware. The compatibility badges and compatibility column in the preview step helps you identify and address any issues before execution.

Executing Bulk Actions

After reviewing the preview, click Execute Bulk Actions to start the operation. Commander will process the actions according to the configured batch size and delay settings.

Actions Log

Actions Log

The Actions Log provides a complete audit trail of every operation executed through Commander. It is accessible in two ways: as a condensed summary at the bottom of the Dashboard, and as a full page with filtering when you click on any action entry.

Actions Table

Each row in the Actions Log represents a single operation and displays:

ColumnDescription
Action TypeThe operation performed - e.g., Power Configuration, Reboot
Created byThe source of the action: Trigger (automated rule), Intelligent Miner (system-initiated), or a user name (manual bulk action). Includes a timestamp
SiteThe Site where the action was executed
AgentThe Agent that carried out the action
MinersThe number of miners affected
StatusThe current state of the action: Completed, In Progress, Waiting, or Failed
ProgressA percentage and progress bar indicating how many miners have been processed

Actions in a Waiting state can be cancelled by clicking the button on the right side of the row.

Action Filters

The Actions Log supports the following filters:

FilterDescription
SitesFilter by one or all Sites
AgentFilter by a specific Agent or all Agents
TimeframeFilter by a predefined time window (e.g., Last 30 days, Last 7 days)
Action TypeFilter by the type of action performed (e.g., Power Configuration, Reboot)

Additional advanced filtering is available via the Action Filters button.

Understanding Action Sources

Actions in the log can originate from three distinct sources:

  • Automation Rule: The action was automatically executed by an automation rule (Trigger/Schedule) when its configured conditions were met.
  • Intelligent Miner: The action was initiated by Commander's intelligent automation system (Intelligent Miner), which autonomously manages miner profile adjustments to maximize fleet profit.
  • User (indicated by a user icon): The action was manually initiated by a user through the Bulk Actions workflow.

Action Details

Clicking any row in the Actions Log opens the Action Details page, which provides a full breakdown of that specific operation - including its configuration, the market conditions at the time of execution (for Intelligent Miner actions), and per-miner results.

Action Summary

The top of the page displays a summary card with the following fields:

FieldDescription
IDThe unique identifier for this action
ActionThe specific remote command executed (Reboot, Change Pool Settings, etc)
StatusThe overall result: Success, Failed, or Completed
AgentThe Agent that executed the action
Created byThe source that initiated the action (user name, Automation Rule, or Intelligent Miner) and the timestamp of execution
Cancelled byIf the action was cancelled, shows who cancelled it; otherwise displays "–"

Depending on the type of action, the summary card includes additional context-specific fields:

For Intelligent Miner actions, a Site Condition section shows the market conditions that were in effect when the optimization ran. This includes Hashprice (/PH/Day),PowerPrice(/PH/Day), Power Price (/MWh), and Max Load (MW). These values explain why the Intelligent Miner chose a particular profile configuration for each miner.

For Bulk Actions and Automation Rule actions, a Parameters section shows the configuration that was applied (e.g., Pool Groups, power target, or mining profile). A Description field may also appear, indicating the name of the Trigger or Schedule rule that initiated the action.

Miner Results Table

Below the summary, a detailed table lists every miner affected by the action with per-miner outcomes:

ColumnDescription
Miner IDThe unique identifier of the miner
Miner IPThe miner's IP address
StatusThe result for this specific miner: Success, Failed, Error, Incompatible, or Offline
ResultDetails about the outcome - for successful Intelligent Miner actions this shows the applied configuration; for failures it shows the error type (e.g., Command Execution Error) and a message

On this page