--- title: "Current Month (November 2026)" slug: "release-notes-current" updated: 2026-11-05T19:12:22Z published: 2026-11-05T19:12:22Z canonical: "support.controlup.com/release-notes-current" --- > ## Documentation Index > Fetch the complete documentation index at: https://support.controlup.com/llms.txt > Use this file to discover all available pages before exploring further. # Current Month (November 2026) ### Pulse AI ### Daily Digest for Insights (Nov 5) You now get a **Daily Digest** in Insights, a once-a-day overview of what was found across your environment. The Daily Digest shows each Insights use case and its run status for the day: - **Completed** use cases show how many insights they generated. If a use case ran but didn't find anything significant enough to generate an insight, the completion message tells you why. This means you can confirm that Insights is working as expected, even on days when no new insights appear. - **Scheduled** use cases that didn't run today show the date of their next scheduled run. - **Failed** use cases tried to run but failed to complete. The completion message tells you why the run failed. ![](https://cdn.document360.io/098100b7-b9da-4bea-b4b9-017140ab863e/Images/Documentation/image-JLPBB45K.png) ### Get alerted on Insights that matter (Nov 5) You can now get email alerts when significant Insights are reported. When you configure an alert rule, select **Insights** as the product, then choose the insight types and severity levels that should trigger the alert. When a matching insight is generated, the alert is emailed to the addresses you specify. ![](https://cdn.document360.io/098100b7-b9da-4bea-b4b9-017140ab863e/Images/Documentation/image-VH06OPCD.png) ### Platform ### [Tenant Manager Blueprints Enhancements](/v1/docs/blueprints) (Nov 3) Blueprints now give you more control when creating and applying configurations: - **Select specific scripts:** When creating a Blueprint, you can choose exactly which scripts to copy from the source tenant instead of including all of them. Use the searchable dropdown to find scripts by name. - **Replace duplicates when adding to existing:** When you use the **Add to existing** deployment mode, you can now select to override existing items when a duplicate is found, so target tenants stay in sync with your latest version. Without it, duplicates are skipped and existing items are left untouched, as before. ### Compliance ### Trust your Compliance results with new scan coverage metrics (Nov 5) Two new columns on the Apps and Issues pages help you verify that your devices are getting scanned so you can trust the results: - **Scanned devices**: The number of devices scanned for the app or issue, compared to the number of eligible devices that weren’t scanned. You can click on the number of not scanned devices to see the list. - **Scan coverage**: The percentage of eligible devices that were scanned for the app or issue. Every device with the Compliance Agent that runs the same OS as the app or issue is eligible. A device doesn’t need to have the app installed, be affected by the issue, or be targeted by a template to count as eligible. Offline devices are included. Both columns use data from the last 30 days. ![](https://cdn.document360.io/098100b7-b9da-4bea-b4b9-017140ab863e/Images/Documentation/image-BMPU3PR4.png) ### Compliance Agent version 1.7.2610.24 (Nov 3) #### What’s new - **Multi-part Windows KBs are installed and reported as one update:** Some Windows KBs are delivered as several sub-patches. The agent now installs and verifies each part and reports a single result for the KB. You see whether the update is fully applied, not a partial picture. ControlUp for Compliance can also send KBs that must be installed in a specific order. The agent installs each KB only after the previous one finishes. - **Side-by-side patches count as remediated only after the app relaunches:** Some apps, such as Google Chrome, install updates side by side. The old, vulnerable version keeps running until the app restarts. The agent now tracks the running process and keeps the remediation open until the old version is no longer running. Tracking continues through a device reboot, an agent service restart, or the user closing the app. Until the old version is gone, the device reports the version that is actually running, so it isn't shown the issue fixed too early. - **Agent-initiated reboots are recorded in the Windows event log:** When the agent restarts a device, it writes Event ID 1074 to the Windows System log with the prefix `[CU4C] REBOOT-`. The entry includes the reason for the reboot and the patches or products involved. You can use it to confirm which restarts came from ControlUp for Compliance and why. - **Faster troubleshooting with ControlUp Support:** The agent now uploads crash dumps and diagnostic logs automatically. Success and failure events also carry the same structured data. ControlUp Support can therefore investigate issues without asking you to collect logs from your devices, and we can detect common failures before they affect you. #### Bug fixes - **Dropped messages between agent components:** Communication between the agent service and its user interface and scanner components could intermittently drop a message. When this happened, a user prompt or agent request failed. - **Version detection for 32-bit apps on 64-bit Windows:** The agent couldn't read the version of a running 32-bit app. Relaunch detection for side-by-side patches didn't work for these apps, and in some cases the agent could become unstable. - **Long reboot and app-close grace periods:** If a reboot or app-close grace period was about 25 days (597 hours) or longer, the reboot, reminder, or snooze timer never fired. The remediation stalled until the agent service restarted. - **Startup failure with an unrecognized cached remediation state:** The agent could fail at startup if its local cache contained a remediation state it didn't recognize, for example after a downgrade from a newer build or a corrupted cache. The agent now logs the unknown state and restarts that remediation. - **Missing vendor and model on older firmware:** Devices with SMBIOS 2.0 through 2.3, such as some older servers, thin clients, and virtual machines, reported an empty vendor and model. - **Incorrect CPU details:** The CPU name and clock speed could be reported incorrectly when the registry values were missing or unusually long. - **App icons:** App icons could be extracted incorrectly from executables that contain fewer small icons than large icons. - **macOS apps with date-stamped versions:** On macOS, the agent failed to read versions such as `1.0.20241015123045` and reported a wrong version for others, such as `2.0.240115`. The agent now reports no version for these apps instead of an incorrect one. - **Rounded-down memory on Windows:** Windows devices rounded total physical memory down. For example, a 16 GB device could report 15 GB and be missed by device filters based on RAM size. Windows devices now round up, the same as macOS and Linux. ### ControlUp for VDI See details in the [Latest VDI Version](/v1/docs/real-time-dx-versions-1) release notes. For previous versions, see [ControlUp for VDI (Real-Time DX versions)](/v1/docs/controlup-for-vdi). For Remote Clients, see [Remote Clients Plugins](/v1/docs/remote-clients-plugins-latest). Go to the [Download Center](https://www.controlup.com/download-center/) to get this latest build for the Real-Time DX Console, Agents and Remote Clients. Need help? Contact your support representative. ### Synthetic Monitoring We continuously release Cloud and Custom hives. To keep your hives and scouts updated, be sure to use the latest and see what we released here: [Cloud and Custom Hive Release Notes](/v1/docs/custom-hive-release-notes). ### Extended API Key Duration for Custom Hives (Nov 3) You can now create Custom Hive registration tokens that remain valid for up to 365 days, increased from 7 days. This allows you to reuse tokens for automated Hive deployments over longer periods without generating new tokens. ### Workflows ### Send Email with SMTP (Nov 5) Workflows now supports sending email using an SMTP server. Configure an SMTP connection and use the **Send Email** action to send HTML or plain-text messages to multiple recipients, including CC and BCC, with optional sender overrides and attachments. ### Flow Completion Notifications (Nov 5) You can now configure notifications in the **Start** node when a flow succeeds or fails. Notifications can be sent via Email, Microsoft Teams, or Slack and include run details such as the flow name, failure information, start and end times, the initiator, and a link to the run. ### DaaS IQ Integration (Nov 5) Workflows now supports **DaaS IQ**. Use **DaaS IQ** actions directly in your flows without configuring a separate integration connection. ### ControlUp Resolve Listener (Nov 5) Workflows can now start a flow when a **ControlUp Resolve** incident is created or an investigation completes. You can filter listener events by status, severity, target, or search criteria. ### Improvements and Fixes (Nov 5) - Improved the Gmail **Send Email** node with recipient chips, collapsed CC/BCC fields, support for uploaded attachments or file URLs, and updated field ordering. - Added search to the **Service**, **Integration**, and **Alert** dropdowns for Listener triggers. - Added a loading indicator to public form pages so users can see when a form is still loading. - Added the **Alert to ServiceNow Incident on the Matching CI** template, which opens a ServiceNow incident from a ControlUp alert and links it to a matching configuration item when available. - **Microsoft Entra ID**: The **List Users**, **List Groups**, and **List Applications** actions now let you choose which fields are returned. Returning all fields remains the default, while selecting specific fields can reduce the response size in large environments.