Updates & Feature Releases 🚀

Time Spread for triggers is rolling out

Time Spread is ready, and we will be rolling it out to customers over the next couple of weeks. If you want to be among the first to beta test it, reach out to your CSM or Support. When you create or edit a trigger on the Triggers page, you can choose to spread its action across a window of time instead of sending it to every matching miner at once. Foreman works through the miners over that window, so a large fleet change lands gradually instead of all in the same moment.

This is built for operators who manage power and performance changes across many machines. Spreading a change out means your whole fleet is not hit in the same moment, and it gives your team room to watch how the first miners respond before the rest follow. Over the past few months, we have tested and refined Time Spread so that it behaves predictably from setup through completion, and you can now follow and control a spread while it runs.

• Spread a trigger's action over a time window: turn on Time Spread when creating or editing a trigger and set the window you want the action to run across.
• Fair ordering: miners are worked through in a random order within the window, so the same machines are not always first or last.
• Edits stay in sync: when you edit a trigger, its spread updates to match, and turning Time Spread off returns the trigger to its normal behavior.
• See what is running: triggers with a spread in progress show an in-progress marker in the Triggers table.
• Follow progress: open a trigger's history panel to see the status of a running spread. The Triggers table and history panel refresh on their own while it runs.
• Cancel at any time: stop a running spread partway through if you need to halt the rollout.
• Clear outcomes: any command that has not finished when the window closes is marked as failed, so you know exactly which miners did not complete. Finished runs remain available to review afterward.

Fixes & Improvements 🛠️

Wattage target commands now wake sleeping miners

• Previously, a PRP wattage target command sent to a miner that was asleep could leave the miner idle. The command now wakes sleeping miners so they come back online at the requested level. PRP wattage commands are also now clearly labeled in Command History, which makes it easier for site operators to tell power-driven changes apart from other commands when auditing activity or troubleshooting a machine.

Ticket-only actions kept when editing or duplicating a trigger

• If a trigger's only action is to create a ticket, that action is now kept when you edit the trigger or duplicate it from the Triggers page. Previously, the ticket action could be dropped, leaving you to add it back by hand. Teams that use triggers purely to open tickets for follow-up can now copy and adjust those triggers with confidence.