Earlier this year, we introduced Trigger Rules in Controlflow, giving mining operators the ability to automate responses to real-time fleet conditions. It was a major step beyond static schedules, but automation is only as powerful as the actions you can take and the conditions you can evaluate.

This update brings new actions, richer conditions, aggregation logic, and direct Telegram notifications to Controlflow, so operators can build smarter automations that cover more of what actually happens on the floor.

New Actions

• Configure pools on targeted devices when conditions are met, whether you're rotating pools, correcting misconfigurations, or reacting to pool-side issues.
• Assign licenses using preset keys, removing a repetitive step from fleet onboarding and maintenance workflows.
• "Do nothing" action for alert-only rules that monitor conditions without executing any action, especially powerful when paired with the new Telegram notifications.

New Conditions

• Pool configuration checks to trigger rules based on whether a device's pool matches or doesn't match a specific configuration.
• License type evaluation to check what Braiins OS license a device is running (e.g., Standard or other preset-defined types) and act accordingly.
• Agent Offline detection to identify devices that have lost communication with Braiins Manager, ideal for building notification alerts.
• Hashing status transitions to trigger rules based on state changes (e.g., from "hashing" to "non-hashing") rather than static values.
• Time range conditions to constrain periodic checks to specific time windows, useful for aligning rules with staffed hours or energy pricing schedules.

Aggregation: Rules That Think Across Your Fleet

Until now, Controlflow conditions evaluated devices individually. With aggregation support, rules can now evaluate conditions across groups of devices, unlocking fleet-level automations.

For example, you can build a rule that triggers when the number of devices transitioning from "hashing" to "non-hashing" exceeds a defined threshold, detecting patterns like a cooling failure affecting an entire row or a network issue taking down a section of your farm. Another rule can monitor total fleet load and trigger when it exceeds your infrastructure capacity.

Aggregation turns Controlflow from a device-level automation tool into one that understands fleet-wide trends, helping operators catch systemic issues earlier.

Telegram Notifications

Controlflow now integrates directly with Telegram, giving teams real-time alerts wherever they are. Connect your Telegram bot in Braiins Manager Settings, then enable notifications on any Controlflow rule. When a rule is activated, you'll receive a Telegram message, whether the rule took an action or used the new "Do nothing" option for monitoring-only alerts.

Other Improvements

• Timezone-aware rules. Each rule stores the creator's timezone, with a UI indicator when your current timezone or DST offset differs from the rule's origin.
• Reorderable rule priorities. When multiple rules target the same device simultaneously, the rule with the highest priority runs and conflicting rules are skipped.
• Target count in rule creation. The number of targeted devices is now visible when creating a rule, so you know what's affected before saving.

Available Now in Braiins Manager

All of these features are live today inside Controlflow. Whether you're managing hundreds or tens of thousands of devices, Controlflow adapts to how your operation actually runs, and now it keeps you informed while it does it.

Many of the improvements in this release were shaped directly by community feedback. Features like aggregation and hashing status transition conditions were among the most requested, and we expedited their implementation to get them into your hands sooner.

If you'd like to help shape the future of Braiins Manager, share feedback with our team or join the discussion in our official Telegram community.