ProVal-Tech · Kamalgurna · Feb 11, 2026 · Feb 13, 2026 · Feb 16, 2026
diff --git a/docs/cwa/monitors/automate-server-unwanted-event-logs-monitoring.md b/docs/cwa/monitors/automate-server-unwanted-event-logs-monitoring.md
@@ -7,7 +7,7 @@ keywords: ['ticket', 'monitoring', 'automate', 'event', 'error', 'critical']
 description: "This document outlines the setup for a remote monitor that generates an urgent ticket in ProVal's Autotask portal when critical events from specified sources occur more than 10 times within 60 minutes on the Automate server. It is specifically designed for On-Prem partners and includes detailed configuration settings and dependencies."
 tags: ['autotask']
 draft: false
-unlisted: false
+unlisted: True
 ---
 
 ## Summary

diff --git a/docs/cwa/monitors/broken-integration.md b/docs/cwa/monitors/broken-integration.md
diff --git a/docs/cwa/monitors/cw-manage-plugin-errors.md b/docs/cwa/monitors/cw-manage-plugin-errors.md
@@ -7,7 +7,7 @@ keywords: ['monitor', 'notification', 'connectwise', 'alerts', 'plugin', 'error'
 description: 'This document outlines the setup and dependencies for an internal monitor that notifies the specified email address of critical errors or issues related to the ConnectWise Manage Plugin. It includes information on the necessary dependencies and the target configuration for global monitoring.'
 tags: ['connectwise', 'email']
 draft: false
-unlisted: false
+unlisted: True
 ---
 
 ## Summary

diff --git a/docs/cwa/monitors/cwm-automate-automate-unsynced-ticket-content.md b/docs/cwa/monitors/cwm-automate-automate-unsynced-ticket-content.md
@@ -7,7 +7,7 @@ keywords: ['monitor', 'tickets', 'alerts', 'synchronization', 'cwmanage']
 description: 'This document outlines the setup and dependencies for the Unsynced Ticket Comments Monitor, which alerts partners about any ticket comments that have not been synchronized with CW Manage. It includes details on required plugins and configuration steps to ensure alerts are sent correctly.'
 tags: ['cwmanage', 'email']
 draft: false
-unlisted: false
+unlisted: true
 ---
 
 ## Summary

diff --git a/...tomate-monitor-failed-email-monitoring.md → docs/cwa/monitors/failed-email-monitoring.md b/...tomate-monitor-failed-email-monitoring.md → docs/cwa/monitors/failed-email-monitoring.md
@@ -1,8 +1,8 @@
 ---
 id: 'f1a15d3d-85d7-4d72-9c08-ad4ca6a7dfbb'
 slug: /f1a15d3d-85d7-4d72-9c08-ad4ca6a7dfbb
-title: 'CWM - Automate - Monitor -Failed Email Monitoring'
-title_meta: 'CWM - Automate - Monitor -Failed Email Monitoring'
+title: 'Failed Email Monitoring'
+title_meta: 'Failed Email Monitoring'
 keywords: ['email', 'ticket', 'monitor', 'failure', 'notification']
 description: 'This document outlines a monitor that reports any failed email occurrences that are not related to specific exclusions. It generates a ticket detailing the failed emails every hour, providing crucial information for troubleshooting and resolution.'
 tags: ['report', 'security', 'setup']
@@ -16,7 +16,7 @@ This monitor reports any failed email that is not related to 'Google Authenticat
 
 Each hour, a ticket with the details of all the failed emails from the previous hour will be generated.
 
-**Ticket Subject:** Automate Failed Email Detected
+**Ticket Subject:** `Automate Failed Email Detected`
 
 **Sample Ticket Body:**
 
@@ -36,7 +36,7 @@ Below is the information of all the emails that failed in the last hour:
   **Subject:** Stuff  
   **Body:** Things  
   **Error Message:** Bad Stuff  
-  **Failure Date:** 2022-07-01 10:03:20  
+  **Failure Date:** 2022-07-01 10:03:20 
 
 ## Important Notes
 
@@ -46,9 +46,8 @@ For hosted partners, it will be the minimum computer ID of Client ID 1. If Clien
 
 ## Dependencies
 
-[Ticket Creation - Without Computer Information And Failures Only [Autofix]](/docs/730449e6-1c73-46ca-a93d-d7b9526e1ef9)
-
-"△ Custom - Ticket Creation - Without Computer Details" alert template should be applied to the monitor set.
+- [Ticket Creation - Without Computer Information And Failures Only [Autofix]](/docs/730449e6-1c73-46ca-a93d-d7b9526e1ef9)
+- `△ Custom - Ticket Creation - Without Computer Details` alert template should be applied to the monitor set.
 
 ## Target
 

diff --git a/docs/cwa/monitors/heartbeat-anomaly-audit.md b/docs/cwa/monitors/heartbeat-anomaly-audit.md
@@ -3,29 +3,29 @@ id: 'fc109cdb-9f88-448b-8c57-b866b2e3c7c2'
 slug: /fc109cdb-9f88-448b-8c57-b866b2e3c7c2
 title: 'Heartbeat Anomaly Audit'
 title_meta: 'Heartbeat Anomaly Audit'
-keywords: ['heartbeat', 'monitor', 'ticketing', 'anomaly', 'autotask']
-description: "This document outlines the implementation of a monitor that creates a ticket in ProVal's AutoTask Portal when fewer heartbeats than expected are detected from machines checking in within the environment. It includes dependencies, target settings, and ticketing details for alerts."
+keywords: ['heartbeat', 'monitor', 'ticketing', 'anomaly']
+description: "This document outlines the implementation of a monitor that creates a ticket in ProVal's Halo PSA when fewer heartbeats than expected are detected from machines checking in within the environment. It includes dependencies, target settings, and ticketing details for alerts."
 tags: ['networking', 'security', 'ticketing']
 draft: false
 unlisted: false
 ---
 
 ## Summary
 
-This monitor is intended to create a ticket in our (ProVal's) AutoTask Portal if there are fewer heartbeats than expected from the machines checking in within the environment.
+This monitor is intended to create a ticket in our (ProVal's) Halo PSA if there are fewer heartbeats than expected from the machines checking in within the environment.
 
 ## Dependencies
 
-[Email RAWSQL Monitor Set Failures* [Autofix]](/docs/901470a2-73d2-4d29-b0d3-c5f15cf19c41)  
-"△ Custom - Email RAWSQL Monitor set results to ProVal" Alert template should be applied.
+- [Script - Email Creation - Computer* [Failure Only]](/docs/901470a2-73d2-4d29-b0d3-c5f15cf19c41)  
+- `△ Custom - Email RAWSQL Monitor set results to ProVal` Alert template should be applied.
 
 ## Target
 
 Global - Should be run without explicitly defined targets.
 
 ## Ticketing
 
-**Subject**: CWA - Heartbeat Anomaly Detected  
+**Subject**: `CWA - Heartbeat Anomaly Detected`  
 
 **Body**: It has been detected that more than half of the agents do not appear to be properly updating their heartbeat, which can cause some false positives with offline alerting:
 

diff --git a/docs/cwa/monitors/screenconnect-broken-integration.md b/docs/cwa/monitors/screenconnect-broken-integration.md
@@ -0,0 +1,24 @@
+---
+id: 'a3e17618-1629-4eca-ae93-e70dd47e3496'
+slug: /a3e17618-1629-4eca-ae93-e70dd47e3496
+title: 'ScreenConnect - Broken Integration'
+title_meta: 'ScreenConnect - Broken Integration'
+keywords: ['connectwise', 'integration', 'ticket', 'monitor']
+description: 'This document outlines the process to create an urgent ticket in ProVal’s Halo PSA for a broken integration between ConnectWise Automate and ScreenConnect. It includes dependencies and target settings for effective monitoring.'
+tags: ['connectwise', 'ticketing']
+draft: false
+unlisted: false
+---
+
+## Summary
+
+This monitor is intended to create an urgent ticket in ProVal's Halo PSA for a broken integration between ConnectWise Automate and ScreenConnect.
+
+## Dependencies
+
+- [Script - Email Creation - Computer* [Failure Only]](/docs/901470a2-73d2-4d29-b0d3-c5f15cf19c41)
+- The `△ Custom - Email RAWSQL Monitor set results to ProVal` alert template should be applied.
+
+## Target
+
+Global - This should be run without explicitly defined targets.
diff --git a/docs/cwa/monitors/scripting-engine-hung.md b/docs/cwa/monitors/scripting-engine-hung.md
@@ -20,8 +20,8 @@ The email is sent to the address specified in the system property `"ProVal_Alert
 
 ## Dependencies
 
-[Scripting Engine Hung - Troubleshooting](/docs/64cf5b44-11bf-42dc-87bc-f1f93582ed8d)  
-**Alert Template:** `△ Custom - Email RAWSQL Monitor set results to ProVal`
+- **Alert Template:** `△ Custom - Email RAWSQL Monitor set results to ProVal`
+- [Script - Email Creation - Computer* [Failure Only]](/docs/901470a2-73d2-4d29-b0d3-c5f15cf19c41)
 
 ## Target
 
@@ -31,14 +31,14 @@ The email is sent to the address specified in the system property `"ProVal_Alert
 
 ### Subject
 ```
-CWA - Scripting Engine Hung
+Urgent! - CWA - Scripting Engine Hung
 ```
 ### Body
 #### Failure
 ```
 %RESULT%
 Troubleshooting Article:
-https://content.provaltech.com/docs/9292f135-cca4-4eba-97ff-cd4276ab62e9#troubleshoot
+https://content.provaltech.com/docs/9292f135-cca4-4eba-97ff-cd4276ab62e9#troubleshooting
 ```
 #### Success
 ```
@@ -55,26 +55,26 @@ Top Script IDs shown below:
 
 ## Troubleshooting
 
-![image](/img/docs/9292f135-cca4-4eba-97ff-cd4276ab62e9/image1.webp)
+![image](../../../static/img/docs/9292f135-cca4-4eba-97ff-cd4276ab62e9/image1.webp)
 
 When you see a ticket like the above for any partner please follow the below troubleshooting steps.
 
-1. Navigate to the System >> VNC / Ticket Priority >> MAX Running Scripts. Look for the "MAX Running Scripts" and ensure its value is at least 1/3 of the value of its agent count. This applies only to the environment where you have seen frequent Scripting Engine Hung issues. This is not a stated statement; rather, it is being assumed to prevent situations in the partner environment if they continuously encounter Scripting engine crash issues. Navigate to the System >> Configuration >> Dashboard >> Config >> Configuration >> Properties. Look for the property "LT_MAXRunningScripts" and ensure its value is reflected
+1. Navigate to the `System` >> VNC / `Ticket Priority` >> `MAX Running Scripts`. Look for the "MAX Running Scripts" and ensure its value is at least 1/3 of the value of its agent count. This applies only to the environment where you have seen frequent Scripting Engine Hung issues. This is not a stated statement; rather, it is being assumed to prevent situations in the partner environment if they continuously encounter Scripting engine crash issues. Navigate to the `System` >> `Configuration` >> `Dashboard` >> `Config` >> `Configuration` >> `Properties`. Look for the property "*LT_MAXRunningScripts*" and ensure its value is reflected
 
-![image](/img/docs/9292f135-cca4-4eba-97ff-cd4276ab62e9/image2.webp)
+![image](../../../static/img/docs/9292f135-cca4-4eba-97ff-cd4276ab62e9/image2.webp)
 
-2. Navigate to the Automation >> Monitor >> Internal Monitor
+2. Navigate to the `Automation` >> `Monitor` >> `Internal Monitor`
 3. Right-click and select the "New Monitor"
 
-![image](/img/docs/9292f135-cca4-4eba-97ff-cd4276ab62e9/image3.webp)
+![image](../../../static/img/docs/9292f135-cca4-4eba-97ff-cd4276ab62e9/image3.webp)
 
 4. Start Fresh >> Next
 
-![image](/img/docs/9292f135-cca4-4eba-97ff-cd4276ab62e9/image4.webp)
+![image](../../../static/img/docs/9292f135-cca4-4eba-97ff-cd4276ab62e9/image4.webp)
 
 5. Run the query as mentioned below. Export the list to share with the consultant. Check for the top scripts whose running count is too much figure out why it has been running like that and fix it if found irrelevant. Bring the concern to the consultant with the note point and screenshots.
 
-![image](/img/docs/9292f135-cca4-4eba-97ff-cd4276ab62e9/image5.webp)
+![image](../../../static/img/docs/9292f135-cca4-4eba-97ff-cd4276ab62e9/image5.webp)
 
 ```sql
 SELECT 
@@ -103,9 +103,9 @@ ORDER BY
 
 6. Run another query. Follow steps 2-4, then run the below query. Please validate the stuck scripts and get that report exported to Excel to forward to the consultant with your feedback and review analysis reporting.
 
-![image](/img/docs/9292f135-cca4-4eba-97ff-cd4276ab62e9/image6.webp)
+![image](../../../static/img/docs/9292f135-cca4-4eba-97ff-cd4276ab62e9/image6.webp)
 
-![image](/img/docs/9292f135-cca4-4eba-97ff-cd4276ab62e9/image7.webp)
+![image](../../../static/img/docs/9292f135-cca4-4eba-97ff-cd4276ab62e9/image7.webp)
 
 ```sql
 SELECT 
@@ -127,4 +127,4 @@ WHERE
   AND CASE WHEN c.lastcontact > NOW() - INTERVAL 15 MINUTE THEN l.ScriptFlags = 0 ELSE l.scriptflags = 1 END
 ```
 
-7. **Only if the scripting engine appears to be hung with a lot of scripts reporting in the queue**, Restart the DB Agent service. Navigate to Help >> Server Status >> Restart Database Agent. This will remove all queued scripts and will fix the script engine hung temporarily if the script queuing issue is not fixed from the above query results.
+7. **Only if the scripting engine appears to be hung with a lot of scripts reporting in the queue**, Restart the DB Agent service. Navigate to `Help` >> `Server Status` >> `Restart Database Agent`. This will remove all queued scripts and will fix the script engine hung temporarily if the script queuing issue is not fixed from the above query results.
diff --git a/docs/cwa/monitors/svc-cwafileservice.md b/docs/cwa/monitors/svc-cwafileservice.md
@@ -4,15 +4,15 @@ slug: /5ae52dd7-e476-49dd-823f-582cbf6de17e
 title: 'SVC-CWAFileService'
 title_meta: 'SVC-CWAFileService'
 keywords: ['monitor', 'service', 'automate', 'ticket', 'status']
-description: 'This document outlines the CWAFileService monitor for the Automate server, detailing its purpose to check the service status and create urgent tickets in Autotask if the service is down, specifically for on-prem partners.'
+description: 'This document outlines the CWAFileService monitor for the Automate server, detailing its purpose to check the service status and create urgent tickets in Halo if the service is down, specifically for on-prem partners.'
 tags: ['ticketing']
 draft: false
 unlisted: false
 ---
 
 ## Summary
 
-CWAFileService is one of the important services for the Automate server. This monitor checks the service status and is intended to create an urgent ticket in our (ProVal's) Autotask portal if it is down. It should be created against the "Labtech Server" group for on-prem partners only.
+CWAFileService is one of the important services for the Automate server. This monitor checks the service status and is intended to create an urgent ticket in our (ProVal's) Halo PSA if it is down. It should be created against the "Labtech Server" group for on-prem partners only.
 
 ## Details
 

diff --git a/docs/cwa/monitors/svc-cwaiismgr.md b/docs/cwa/monitors/svc-cwaiismgr.md
@@ -4,15 +4,15 @@ slug: /f73d6546-470e-448b-b3db-d7b57d3d8df4
 title: 'SVC-CWAIISMgr'
 title_meta: 'SVC-CWAIISMgr'
 keywords: ['monitor', 'service', 'automate', 'ticket', 'labtech', 'server']
-description: 'This document outlines the CWAIISMgr service monitor for the Automate server, detailing its purpose, configuration, and alert settings to ensure timely ticket creation in the Autotask portal when the service is down.'
+description: 'This document outlines the CWAIISMgr service monitor for the Automate server, detailing its purpose, configuration, and alert settings to ensure timely ticket creation in the Halo PSA  when the service is down.'
 tags: ['windows']
 draft: false
 unlisted: false
 ---
 
 ## Summary
 
-CWAIISMgr is one of the important services for the Automate server. This monitor checks the service status and is intended to create an urgent ticket in our (ProVal's) Autotask portal if it is down. It should be created against the "Labtech Server" group for the on-prem partners only.
+CWAIISMgr is one of the important services for the Automate server. This monitor checks the service status and is intended to create an urgent ticket in our (ProVal's) Halo PSA if it is down. It should be created against the "Labtech Server" group for the on-prem partners only.
 
 ## Details
 

diff --git a/docs/cwa/monitors/svc-cwamessagequeue.md b/docs/cwa/monitors/svc-cwamessagequeue.md
@@ -4,15 +4,15 @@ slug: /a1fb4b3c-b08f-4090-9df7-66e7d80ca93d
 title: 'SVC-CWAMessageQueue'
 title_meta: 'SVC-CWAMessageQueue'
 keywords: ['cwa', 'monitoring', 'service', 'alert', 'ticket']
-description: 'This document outlines the monitoring setup for the CWAMessageQueue service in ConnectWise Automate. It details the alert configuration, suggested parameters, and target server roles to ensure timely notifications and ticket creation in Autotask when the service becomes unavailable.'
+description: 'This document outlines the monitoring setup for the CWAMessageQueue service in ConnectWise Automate. It details the alert configuration, suggested parameters, and target server roles to ensure timely notifications and ticket creation in Halo when the service becomes unavailable.'
 tags: []
 draft: false
 unlisted: false
 ---
 
 ## Summary
 
-CWAMessageQueue is one of the important services for the Automate server. This monitor is intended to alert on the status of that service and create an urgent ticket in our (ProVal's) Autotask portal in the event that the service becomes unavailable. It should be created against the "Labtech Server" group for the on-prem partners only.
+CWAMessageQueue is one of the important services for the Automate server. This monitor is intended to alert on the status of that service and create an urgent ticket in our (ProVal's) Halo PSA in the event that the service becomes unavailable. It should be created against the "Labtech Server" group for the on-prem partners only.
 
 ## Details
 

diff --git a/docs/cwa/monitors/svc-ltredirsvc.md b/docs/cwa/monitors/svc-ltredirsvc.md
@@ -4,15 +4,15 @@ slug: /33120745-9fa1-4864-aff6-b97d083e3fd5
 title: 'SVC-LTRedirSVC'
 title_meta: 'SVC-LTRedirSVC'
 keywords: ['automate', 'monitoring', 'service', 'alert', 'ticket']
-description: 'This document outlines the monitoring setup for the LTRedirSVC service on the Automate server, including alert configurations and service check details to ensure timely notifications and ticket creation in Autotask.'
+description: 'This document outlines the monitoring setup for the LTRedirSVC service on the Automate server, including alert configurations and service check details to ensure timely notifications and ticket creation in Halo.'
 tags: []
 draft: false
 unlisted: false
 ---
 
 ## Summary
 
-LTRedirSVC is one of the important services for the Automate server. This monitor is intended to alert on the status of that service and create an urgent ticket in our (ProVal's) Autotask portal if the status becomes failed.
+LTRedirSVC is one of the important services for the Automate server. This monitor is intended to alert on the status of that service and create an urgent ticket in our (ProVal's) Halo PSA if the status becomes failed.
 
 It should be created against the "Labtech Server" group for on-prem partners only.
 

diff --git a/docs/cwa/monitors/ticket-sync-unsuccessful.md b/docs/cwa/monitors/ticket-sync-unsuccessful.md
@@ -7,7 +7,7 @@ keywords: ['ticket', 'sync', 'monitor', 'psa', 'automate']
 description: 'This document outlines a monitor for identifying tickets within ConnectWise Automate that have failed to sync successfully to the PSA. It includes dependencies and target details for effective implementation.'
 tags: ['connectwise']
 draft: false
-unlisted: false
+unlisted: true
 ---
 
 ## Summary

diff --git a/docs/cwa/scripts/automate-server-event-log-monitoring-autofix.md b/docs/cwa/scripts/automate-server-event-log-monitoring-autofix.md
@@ -7,7 +7,7 @@ keywords: ['event', 'logs', 'monitoring', 'alert', 'script']
 description: 'This document describes a script designed to monitor unwanted event logs in the Automate Server environment. It provides details on how the script functions, its dependencies, and the process it follows to alert users when unwanted logs are detected.'
 tags: ['email']
 draft: false
-unlisted: false
+unlisted: true
 ---
 
 ## Summary