Release v0.127.0
Nov 07, 2026
Restore browsing and search for backup snapshots of any size, live backup progress with plain failure reasons, a new SLA performance report, partner-wide alert lifecycle defaults, Axcient x360Recover as a backup provider, and Breeze AI that runs patch plans, checks backups and manages organization settings with approvals. Alert notifications that were being silently dropped now go out, so review your routing before you upgrade.
Alerts & Notifications
- Read before you upgrade: most monitor and system alerts were being created without sending their notifications. That is fixed, so after the upgrade alerts that only appeared on the Alerts page will send in-app, email, SMS, Slack, Teams, PagerDuty, Pushover, webhook and escalation notifications. SMS costs money and on-call staff may be paged for alerts that were quiet before, so review notification routing, monitor delivery settings and escalation policies first. Only alerts raised after the upgrade send, so there is no backlog burst.
- Alerts → Monitors → Lifecycle defaults sets cooldown, auto-resolve and re-arm once as a partner default, with per-organization overrides. Any monitor can still override them, and existing monitors behave exactly as before until you change a default.
- Re-arm an alert on new evidence, or after a set number of minutes once it has closed. An open alert keeps the lifecycle it was raised with, even if you change the defaults later.
- Event-log monitors can name the event that clears an alert, for example a UPS's Power Restored event.
- Monitor this on Remote Tools → Services and Processes starts a service or process monitor already filled in with that name.
- Scheduled IOC and sensitive-data scans now run at their configured times. Expect those scans, and their device load, after the upgrade if you have scheduled scan policies.
Backup & Recovery
- Restore browsing works on every backup snapshot on S3-compatible storage, whatever its size and including snapshots taken before this release. We tested it with snapshots of over a million files. Before, a snapshot with more than about 10,000 files showed an empty or partial file list.
- Search a snapshot by file name or path, and restore a whole folder with everything under it.
- The first time you browse a large snapshot, Breeze prepares its file list and shows its progress, with Try again if that fails.
- The device page shows running and waiting backups with phase, progress, speed and time left, plus a Backup running badge in the device header.
- Failed, partial and cancelled backups give a plain reason such as Device offline, Storage problem or Agent problem, with a hint and a link to the troubleshooting guide.
- Each backup run shows how much it uploaded and how much it reused from earlier backups. A run that uploaded everything is marked Full, with the reason.
- A scheduled backup on a device that is off at its scheduled time waits for the device to come back, for up to 20 hours or until the next scheduled run, instead of failing. You can turn this off per schedule.
- Axcient x360Recover joins Cove and NinjaOne SaaS Backup (Dropsuite) as a backup provider, showing device status, including paused devices, and the last verified-bootable check. The connection reads status only, and nothing changes until you add an Axcient connection.
- Long backup resumes keep reporting progress and are no longer cancelled as stale, and an interrupted resume keeps its saved state.
Reporting & Service Delivery
- SLA performance report: response and resolution times against SLA for one organization, by priority, with the breaches listed. Schedule it, email it and export it. Ticket subjects are left out by default.
- A service plan can deliver the SLA performance report as evidence each period, and customers see it in their portal once you deliver that period.
- The logo and secondary colour you set under Settings → Branding now appear in that customer's portal, quotes, invoices and report PDFs, falling back to your partner branding.
- The partner dashboard shows real open-alert counts and compliance for each customer.
- Microsoft 365 email-to-ticket verifies external senders with Exchange Online's own DMARC result, and accepts a trusted mail gateway you list on the mailbox card. Before, all external mail was quarantined.
- Connecting a Microsoft 365 support mailbox no longer turns its existing mail into tickets. Only mail received after you connect does.
- A new permission lets a custom role or service account triage the inbound email Review queue without full admin rights.
Breeze AI
- Run an organization's patch plan, or start an AI task that gets a stopped service running again. Starting either takes one approval, and every install or change the run proposes needs its own.
- Schedule AI agent runs, and preview, apply, undo and file Fleet Designs. Deleting a schedule, applying a design and undoing one each need a second approver.
- Check backups from chat: backup verification, VSS writer status, bare-metal recovery history, cloud-to-cloud backup configurations and backup health.
- Look up an organization's summary, account readiness, audit-log retention, portal logins, and Breeze users and roles. User and role changes stay in Settings.
- Change an organization's customer portal settings and a scheduled report's email recipients. Turning on sensitive portal data needs two approvers.
- When a partner technician asks the assistant to change a different organization from the one their session is open on, the approval goes to that organization's approvers.
- Partner Settings → AI Budgets has a clear AI for all organizations switch (Not set, On, Off), and Off asks you to confirm.
- On self-hosted OpenAI-compatible models, Breeze fits its requests to the model's context window and says clearly when a prompt is too large.
- Wisp (Breeze Cloud) can schedule its own check-ins, brings in a device-troubleshooting specialist with step-by-step approvals, and offers a plain Breeze AI chat beside an active grant.
Devices & Remote Access
- Waking a device that is already online is skipped, bulk wakes report how many were sent and skipped, and every wake records whether the device came online.
- The product number (HP product number, Lenovo and Dell machine codes) appears beside the serial number in Device Details, as a Devices column, in CSV exports and in reports. Needs the 0.127.0 agent.
- New folder in the device file browser.
- Add Device shows the install token and installer link you created earlier for a site while they are still valid.
- UniFi Wi-Fi telemetry on the Deep telemetry card: access point status and uptime, wireless clients, radio band, channel and retries, CPU, memory and uplink rates.
- A remote desktop viewer that loses its connection reconnects to the same session instead of reporting that the session ended, and reconnecting no longer restarts the session's maximum duration.
- Each signed-in user gets their own request budget, so technicians behind one office connection no longer slow each other down. A page that is briefly rate-limited waits and retries instead of showing Failed to load.
Agent & Platform
- On Windows, Breeze Assist waits for a signed-in user, so machines with nobody signed in stop reporting a false crash loop.
- The Windows local admin audit recognises the built-in Administrator and Guest accounts and flags them when they are enabled.
- A Windows agent self-update that did not take effect is reported once with its reason and retried with back-off.
- Physical-keys mode types punctuation correctly on AZERTY and other non-US keyboard layouts.
- Fewer wasted checks: the Security Center query is skipped on Windows Server, and periodic probes stop retrying tools that aren't installed.
- Linux firewall inventory works when ufw and firewalld can't answer, and macOS users with no crontab no longer show an error.
- Permanently deleting a device now asks for confirmation when its agent never confirmed the uninstall, so a device can't vanish from Breeze while its agent keeps running.
- Security hardening across AI approvals, the agent and Breeze Assist, device deletion, DNS Security and dependency updates. Self-hosters are encouraged to upgrade.
Read before you upgrade: alert notifications that were being dropped now go out. Since the alert pipeline rewrite, most monitor and system alerts were raised without sending their notifications, so you only saw them on the Alerts page. v0.127.0 fixes that. After the upgrade those alerts send email, SMS, chat, webhook and escalation notifications like any other. SMS costs money and on-call staff may be paged for alerts that were quiet before, so review your notification routing and escalation policies first. Only new alerts send, so there is no backlog burst. While you’re there, the new Lifecycle defaults page lets you set cooldown, auto-resolve and re-arm once for every organization.
Backups get much easier to watch and to restore from. The Snapshot Browser now works on S3 snapshots of any size, including ones taken before this release, adds search, and restores whole folders. The device page shows what a backup is doing right now and why a failed one failed, in plain words. A scheduled backup on a device that was off waits for it to come back, and Axcient x360Recover joins Cove and NinjaOne SaaS Backup as a provider. A new SLA performance report shows response and resolution against SLA by priority, and you can schedule it, email it, or deliver it to the customer portal each period. Breeze AI can now run patch plans, check backup health and change organization settings, with every change approved and a second approver for the risky ones.
Known issues: Excel downloads of a stored SLA performance run leave out the breaches sheet (the on-screen report and PDF are complete), and on self-hosted installs server-generated report PDFs can fail, as they also did in v0.126.0. Both are fixed in v0.127.1. On a Mac, Shift can stay held in a remote session after its first press. That issue predates this release, and a fix is in review. Self-hosters: run bash guided-setup.sh --upgrade 0.127.0, or on tag-form installs set BREEZE_VERSION=0.127.0 and pull api, web and portal. There are no new required environment variables. The 31 migrations apply automatically and are idempotent, and three of them briefly lock a busy table, so upgrade in a quiet hour if your install is large. The GitHub release notes have the full upgrade detail.