• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar
  • Skip to footer
ControlUp Community

ControlUp Community

Connect, Learn, and Grow

  • Blog
  • Archives
  • Findings
  • Meetups
  • Videos
  • Events
  • Categories
    • ControlUp One Platform
    • ControlUp for Apps
    • ControlUp for Compliance
    • ControlUp Dashboards
    • ControlUp for Desktops
    • ControlUp for VDI
    • ControlUp Scripts & Triggers
    • ControlUp Synthetic Monitoring
    • ControlUp Workflows
  • Topics
    • Logos & Wallpaper
    • ControlUp.com
  • Join

Triggers Related Training & Support Archives

Triggers training and support-related archives from inside the ControlUp Community on Slack.


ControlUp Community Meetup #18 — ControlUp Workflows in Action | Live Demos & Community Q&A

Posted on November 12, 2026

In this ControlUp Community Meetup, we walk through the drag-and-drop workflow builder and demonstrate how triggers, actions, and logic work together—from responding to an alert to managing a password-expiry process. Read the entire article here...

Handling Alert Storms and Outages in ControlUp Scoutbees: Current Best Practices and Upcoming Features

Posted on November 11, 2026

During an internet connectivity outage in Italy, a large volume of Scoutbees alerts was triggered due to multiple login request failures, resulting in an alert storm. This situation prompted a request for a dependency model that would suppress downstream alerts when a critical component like a gateway is detected as unavailable. Alternatively, the user inquired about automatically triggering a maintenance window to temporarily disable alerts for affected scouts during such outages. To address this, the current recommended approach involves tuning alert settings to reduce noise while preserving important signals. Key adjustments include configuring alerts to notify only when test results return to normal, thereby limiting notifications to one alert at the start of an issue and one upon resolution. Additionally, increasing the threshold for consecutive failed tests before sending an alert helps ignore brief transient failures but still catches sustained outages. These simple changes significantly reduce alert volume during connectivity issues without missing critical events. Looking ahead, the ControlUp team is actively developing a feature to enable maintenance windows by tag. This will allow users to silence all scouts associated with a specific tag—such as “italy”—with a single action during known problems or outages. This functionality aims to streamline manual alert silencing in complex environments without risking important signals being suppressed automatically. Automatic suppression of downstream alerts in the event of gateway failure is discouraged since synthetic monitoring is designed to reflect real user experience, and connectivity failures are essential to surface. Until the tag-based maintenance feature becomes available, the user opted to implement manual maintenance windows that disable alerts during outages to avoid missing issues outside planned maintenance periods. The approach balances the need to reduce alert fatigue while ensuring critical incidents are not overlooked. The ControlUp team remains open to direct conversations with users to refine upcoming features for scenarios such as this. For further detail on tuning Scoutbees alerts and maintenance windows, see the ControlUp documentation at https://docs.controlup.com. The upcoming maintenance-by-tag feature will enhance flexibility in managing alert noise during large-scale or regional disruptions. Read the entire article here...

Handling Duplicate Entries in ControlUp Custom Dashboards with Time-Series Data Aggregation

Posted on November 3, 2026

In a ControlUp Community discussion, a user presented a scenario involving a custom data index used to track daily speed test results—upload speed, download speed, and latency—recorded per computer. The data is accumulated over time without overwriting previous entries, enabling the calculation of 30-day averages and trend analysis. However, when visualizing this data on custom dashboards with multiple panels like gauges, tables, and grids, the user encountered the problem of duplicate entries for the same computer appearing multiple times within the selected date range (e.g., last 10 days). The challenge was to display only the most recent entry for each computer while preserving all historical data in the index. The core insight shared by community members was that raw data views such as grids inherently show all individual records, which results in duplicates when multiple entries per device exist over the date range. To resolve this, it is recommended to use aggregation functions that summarize data at the device level rather than displaying raw records. Aggregates can consolidate multiple entries for the same device, ensuring that each device appears only once, typically reflecting a calculation like the most recent value or an average over the period. A practical suggestion was to avoid the raw grid view for this purpose and instead configure the dashboard panels to aggregate results based on a unique device identifier, such as device_id, rather than the device name. Aggregating on device_id ensures that all entries related to the same device are grouped properly. This method allows viewers to see one summarized record per device that represents the latest or otherwise relevant aggregated values. Without access to the user’s custom index or dashboard JSON configuration, the community could not provide a definitive tweak but highlighted the importance of aggregation and key field selection. This approach maintains the historical dataset intact, supporting trend analysis while enabling concise visualization devoid of duplicate device entries. Users working with ControlUp custom indexes and dashboards that store multiple time-series records per device should leverage aggregation functions on unique device identifiers within their panels to effectively manage display deduplication over time. For further guidance on using ControlUp dashboards, filters, and aggregation functions, see the ControlUp documentation at https://docs.controlup.com and ControlUp Academy tutorials at https://cuacademy.controlup.com. Read the entire article here...

Automating Windows 365 Cloud PC Rightsizing with AI Canvas: Cost and Performance Optimization

Posted on November 3, 2026

A new AI prompt has been developed for ControlUp's AI Canvas to automate the rightsizing evaluation of Windows 365 Cloud PCs within an organization. The prompt identifies every Windows 365 Cloud PC, determines its current plan based on CPU, RAM, and storage configuration, and analyzes recent performance metrics to assess whether the plan suits the workload. It estimates the potential savings or costs associated with resizing each Cloud PC and presents the results along with actionable recommendations. The process begins by querying all Cloud PCs configured with the Microsoft Cloud PC provider. Devices not reporting back within the last 14 days are excluded from sizing recommendations but flagged separately since they may still incur licensing costs despite inactivity. The prompt calculates usage metrics over a recent 7-day window, focusing on CPU load (p95) and memory utilization (p95), plus storage consumption on the system disk. Oversizing is flagged when CPU and memory usage consistently remain low (under specified thresholds), prompting recommendations to downgrade one step in the plan ladder if the workload still fits comfortably within the smaller configuration. Conversely, oversizing occurs if resource usage exceeds defined upper limits, triggering an upgrade suggestion. Storage sizing is handled separately, moving devices to plans with appropriately sized storage tiers based on usage, with thresholds designed to avoid undersized or oversized drives. Pricing uses Microsoft’s public Windows 365 Enterprise list prices as of November 2026, converted into cost differences reflecting the proposed resizing changes. The prompt outputs a comprehensive dashboard including a net monthly savings stat, a donut chart categorizing Cloud PCs by sizing verdict (right-sized, oversized, undersized, storage too small/large, not reporting, or unmatched), and a detailed table for all devices showing current and recommended plans, verdicts, pricing impact, VM size, region, and storage type. An AI-generated summary provides holistic findings, including potential savings, constraints on high-demand users, and caveats such as volume licensing discounts and workload peaks outside the measurement window. Testing in lab environments indicates the prompt works reliably, producing clear and actionable results within acceptable execution times. Feedback suggested that the visual emphasis on total savings paired with detailed explanations improved usability. The solution currently covers Enterprise licenses only, with Business and Frontline licenses excluded from analysis, and the pricing reflects list prices that may differ from negotiated agreements. This prompt is intended to run as a single AI Canvas operation with efficient batch querying to stay within API limits, making it scalable for real-world tenant environments. This AI prompt for Windows 365 rightsizing represents a powerful tool to optimize Cloud PC deployment costs and performance by providing IT teams with data-driven resizing recommendations and potential financial impact upfront. Further refinements may include extending support for additional license types and adjusting resource thresholds as usage patterns evolve. For more information about Windows 365 Cloud PCs and rightsizing, see the official Microsoft documentation: https://docs.microsoft.com/en-us/windows-365/right-sizing-cloud-pc and ControlUp resources at https://docs.controlup.com. Read the entire article here...

How to Use ControlUp AI Decision Nodes to Trigger Conditional Script Execution in Automated Workflows

Posted on November 3, 2026

A user sought advice on creating an automated workflow in ControlUp that uses the AI node to diagnose issues and then runs specific scripts based on the AI’s suggested solutions. The user wanted the flow to dynamically execute one or two scripts out of a set of five, depending on whether the AI recommended actions such as a repair or a driver update. The solution involved leveraging an AI decision node within ControlUp’s automation workflow. This AI decision node allows the configuration of custom questions and multiple outputs based on the AI’s analysis. By setting conditions within this node to evaluate the AI’s recommended solution, the workflow can branch and trigger particular script nodes accordingly. Using the AI decision node to branch the workflow, users can effectively map various AI-generated solutions to corresponding remediation scripts. For example, if the AI suggests a system repair or a driver update, the flow can be directed to execute the relevant script via a run script node. This approach supports flexible and conditional automation based on AI diagnostics within ControlUp’s process automation environment. Overall, integrating the AI decision node with conditional outputs enables sophisticated, solution-driven scripting workflows. Users can build customized automation flows that respond dynamically to AI findings, improving IT issue resolution efficiency. For more detailed instructions on AI node configuration and automation flows, users should reference ControlUp’s official documentation and resources such as https://docs.controlup.com. Read the entire article here...

Understanding ControlUp Compliance Update Latency and Best Practices for Timely Patching

Posted on October 29, 2026

When organizations use ControlUp for Compliance to monitor and manage application updates, a common question arises regarding how quickly updates, such as security patches for applications like Google Chrome, become available through the platform’s compliance module. This is particularly important when timely patching is critical to address vulnerabilities identified by CVEs. The update availability process in ControlUp for Compliance involves several stages. First, a new application version must be included in the patch catalog, which is derived from a third-party patch feed. The speed at which a new version appears in this feed varies by application vendor and release and is outside ControlUp’s direct control. For major browsers like Chrome, this step is typically quick but not guaranteed within a specific timeline. Once the patch feed updates, ControlUp scans it every three hours to update the catalog. The tenant then checks for a catalog update approximately every hour, resulting in roughly a four-hour delay on ControlUp’s side before the tenant receives the latest version information. After that, devices report their compliance status based on their scanning schedule, meaning the frequency with which devices scan for updates directly impacts how soon they reflect new versions. The installation or remediation of updates follows according to template settings, including remediation windows and any manual triggers from administrators. For sensitive environments requiring rapid response, such as those impacted by CVEs, recommendations include increasing scan frequency to daily or more, configuring remediation windows to allow timely installations, and leveraging the ControlUp Content Delivery Network (CDN) with the “Allow CDN bypass for self-updating applications” option (available starting with agent version 1.6). This setting enables applications like Chrome to update directly from the vendor, speeding up patch delivery. Additionally, maintaining the application’s native auto-update functionality provides a primary defense layer, with ControlUp Compliance providing oversight to catch devices where auto-update failed. In practice, new Chrome updates have been observed to appear in Compliance the day after a vendor’s release, although this example should not be considered a guaranteed SLA due to variations in vendor feeds and catalog processing times. Windows patching follows a similar cadence, typically aligned with Microsoft’s Patch Tuesday schedule, and similarly may take up to three days to reflect in the catalog after release. Further details on scheduling scans and managing templates in ControlUp for Compliance are available in the official documentation here: https://support.controlup.com/docs/controlup-for-compliance Read the entire article here...

Enhancing Update Control in ControlUp Compliance Agent: User Request for Manual Update Initiation Before Snooze Expiry

Posted on October 21, 2026

A user at the University of Pennsylvania School of Medicine shared feedback regarding the ControlUp compliance agent installed on their computer to manage software updates. The primary issue reported was that while the agent provided notifications about pending updates and allowed snoozing them, there was no mechanism to initiate the update manually before the snooze period expired. This created a challenge for users like statisticians who keep long-running analysis sessions open and prefer to update at specific, convenient times without forced restarts interrupting their work. The user requested one of two improvements: either enabling a way to revisit the notification after snoozing so they could start the update on demand, or having the compliance agent queue the update to trigger automatically upon the first manual restart occurring before the snooze period ends. This functionality would give users the flexibility to apply updates immediately when they choose, avoiding unexpected disruptions while still deferring updates if necessary. ControlUp support engaged by asking for the organization name and requesting logs from the device in question to investigate the behavior further. The user clarified that no logs were clearly visible and only the notification and snooze options appeared. The support team then inquired about the presence of log files in the ControlUp compliance agent's log directory located at C:\ProgramData\ControlUp\CU4DC\Logs, which is where relevant diagnostic data might be stored to better understand the update management interactions. This discussion highlights an area for product enhancement around update scheduling within the ControlUp compliance agent. Currently, the update snooze feature lacks a proactive user control to manually trigger pending updates outside the original snooze timing. Users who rely on long-duration sessions or need precise control over disruptive restarts may find this limiting. Including the ability to either resume update installation on demand after snoozing or to ensure updates proceed on the next manual system restart would address these concerns and improve user experience in environments with sensitive workflows. For administrators managing ControlUp compliance agent deployments, checking the client log directory at C:\ProgramData\ControlUp\CU4DC\Logs can assist in troubleshooting update notification and enforcement issues. Until this feature is added, coordinating the timing of forced updates with end users who require flexible update start times is advisable to minimize work interruptions. More details about ControlUp Compliance Agent and managing update behavior can be found in the official documentation at https://docs.controlup.com/compliance-agent. Users seeking advanced update control features can also explore ControlUp’s community forums and support channels for the latest product enhancements and best practices. Read the entire article here...

Maximizing Employee Experience Insights with ControlUp: Key Features, Metrics, and Best Practices

Posted on October 20, 2026

ControlUp users focusing on digital employee experience (DEX) and user experience monitoring have found several features and best practices especially valuable for measuring adoption, engagement, and satisfaction across their environments. Key recommendations center around combining telemetry data with direct user feedback such as surveys to obtain richer insights. Surveys are most effective when paired with quantitative telemetry metrics, as this correlation reveals gaps and areas for improvement that neither approach alone can fully expose. A primary metric endorsed by the community is the DEX Score, which aggregates user experience data into a single score per user, and can be rolled up by department, location, or persona. Trending DEX Scores over time provides a clear adoption and satisfaction narrative. In addition, monitoring logon duration per group is critical because delays here are a common source of user frustration and complaints. For user experience visibility, the Employee View dashboard enables IT teams to quickly identify issues impacting end users. Other frequently cited dashboards include those focusing on Windows application crashes, app stability and performance, AI-driven apps and sites usage, and Teams/Unified Communications call quality—particularly important for organizations heavily reliant on Microsoft Teams. Anomaly detection using AI (Pulse AI) is recommended over static threshold alerts, as it can find unusual patterns proactively and even suggest or enact fixes via workflows. Custom dashboards should be tailored to different stakeholders—executive views showing aggregated DEX by business units, operational views tracking logon times and resource usage, and user experience views combining app performance and user sentiment. In addition, creative use of automation workflows can significantly enhance support responsiveness. For example, a self-healing workflow can collect diagnostic data on machine issues, generate AI-driven recommendations, automatically open service tickets (e.g., in ServiceNow), and notify users with remedial steps before they contact helpdesk. Integrations such as with ServiceNow enable automated ticket creation and remediation workflows that improve IT support efficiency and end-user communication. ControlUp roles can be customized to give access across teams (security, network, telephony) beyond just helpdesk functions, helping different groups leverage relevant telemetry. New users of ControlUp are advised to start with free courses available at ControlUp Academy, followed by hands-on evaluation of dashboards in the Dashboard Gallery to understand available data and refine dashboards per organizational needs. Building out use cases and dashboards incrementally—starting with a few key metrics and expanding gradually—helps organizations avoid measurement overload and focus on actionable insights. Finally, community insights emphasize ongoing management of user personas underpinning DEX Score segmentation, with approaches varying from manual updates to bulk imports depending on organizational scale. Overall, a combined strategy using ControlUp’s telemetry, custom dashboards, integrations, AI-powered anomaly detection, and employee survey data provides a powerful framework for measuring and improving employee experience in IT environments. Relevant resources include: ControlUp Academy: https://cuacademy.controlup.com ControlUp official documentation: https://docs.controlup.com ControlUp Community: https://community.controlup.com Dashboard Gallery (within ControlUp platform) Read the entire article here...

Resolving ControlUp API Rate Limit (HTTP 429) Errors in Automated Workflows

Posted on October 19, 2026

Users reported intermittent "HTTP 429 Too Many Requests" errors when using the ControlUp API, specifically receiving the message "Rate limit is exceeded. Try again in 1 seconds." These errors caused temporary failures in workflow steps that interact with the API. The issue was sporadic, occurring some weeks but not others, indicating periods when API request volume exceeded the allowed quota. The root cause was identified as ControlUp's API rate limiting, which enforces a maximum number of API calls per unit time to prevent overload. When the limit is exceeded, subsequent requests receive the 429 error code, prompting automated retries that either delay the workflow or result in transient failures. The error message suggests reducing the frequency of workflow runs or checking the integration’s API quota if the problem persists. ControlUp’s support team investigated the situation for the affected organization. They confirmed the rate limits were being hit and subsequently increased the API quota allocated to the organization. This quota increase was intended to accommodate the higher volume of API requests and prevent recurring rate-limit errors. Users were advised that no immediate changes on their side were required, but to report any further occurrences with details such as the specific workflow name and timestamp to facilitate further analysis. Following the quota increase, the frequency of 429 errors dropped significantly, and workflows resumed normal operation. ControlUp recommends monitoring workflow execution and maintaining awareness of API call volumes to avoid hitting limits in the future. For more information on managing API rate limits and workflow best practices, users can consult the official ControlUp documentation available at https://docs.controlup.com. Detailed troubleshooting steps and how to interpret API error responses are also covered there to assist with addressing similar issues. Read the entire article here...

Understanding and Resolving Missing Node References Caused by Output Variables in ControlUp Workflows

Posted on October 16, 2026

A user encountered an issue where a ControlUp workflow, previously used to push alert messages to Google Chat, stopped functioning correctly. The workflow's start node began reporting a reference to a missing node, a problem not seen before. This issue coincided with the use of output variables in the workflow. Removing these output variables stopped the error messages, though including them had been necessary for the workflow to work previously. The output variables in ControlUp workflows are primarily designed for use with subflows, where a subflow acts like a function by taking input, processing it, and returning data to the main flow. The output variables specify what data the subflow returns. However, in this case, the workflow was not a subflow, and the user was instructing the workflow to return properties from an event variable that could not be found. This discrepancy caused the workflow to flag missing node references. A newer validation check within ControlUp appears to verify if workflows reference variables that do not exist. This validation is likely why the error started appearing even though the workflow continued to run and post messages correctly. Before this update, referencing nonexistent variables was silently ignored, causing no breakage. Therefore, although the output variables cause no functional harm in a non-subflow context, they create misleading error states that might confuse anyone reviewing or maintaining the workflow. The recommended resolution is to delete the output variables whenever the workflow is not a subflow. Removing these output variables prevents confusion and stops error messages related to missing nodes without impacting the workflow’s functionality. Users needing to troubleshoot similar issues should also consider exporting the workflow in JSON format and providing run history details when contacting ControlUp support. For more on ControlUp workflows, output variables, and subflows, refer to the official documentation at https://docs.controlup.com. Read the entire article here...
  • Page 1
  • Page 2
  • Page 3
  • Interim pages omitted …
  • Page 39
  • Go to Next Page »

Primary Sidebar

ControlUp Academy

Enroll in ControlUp Academy for expert-led technical training, equipping you with skills to effectively deploy, manage, and grow your ControlUp investment.

Learn here >

Rotating Images

Hidden Gem from our Community on Slack!

ControlUp Betas - What's Coming Next?
NEW ControlUp Features - Stay Up-to-Date!
ControlUp Scripts - Scripting, Zero to Hero
Latest KB Articles - Be the First to Learn

Video Tutorials Library

Visit our technical how-to videos, offering step-by-step tutorials on advanced features, troubleshooting, and best practices.

Watch here >

ControlUp Blog

Check out the ControlUp blog for expert advice and in-depth analysis.

Read here >

ControlUp Script Library

Visit the ControlUp technical script library, which offers a multitude of pre-built scripts and custom actions for your monitoring and troubleshooting requirements.

See here >

ControlUp Support

Visit the ControlUp support home and to delve deeper into ControlUp DEX solutions.

Browse here >

Footer

      

ControlUp Community
Of Techie, By Techie, For Techie!

Terms of Use | Privacy Policy | Security
Dive Deeper, Learn more at ControlUp.com

  • facebook
  • twitter
  • youtube
  • linkedin

© 2023–2026 ControlUp Technologies LTD, All Rights Reserved.

We use cookies to ensure that we give you the best experience on our website. by continuing to use this site you agree to our Cookie policy..