Can we have a parameter that says that we only get notifications when a remote PC has been off line for say 15 minutes, and we only receive a reconnection notification if it has been off line for more than 30 minutes?
We have setup the triggers that seem to be working well. However due to temporary fluctuations in the internet connections we receive disconection notifications with almost immediate reconnections only a few seconds apart.
We have a trigger that notifies us when machines go offline or online however when we need to restart the ScreenConnect server it spams us. Could we have a delay when the server starts before triggers start working? In the same area could we have the option to have the server disable triggers when the ScreenConnect server is being shutdown?
Please add the ability to have a delay option in your triggers! I use the Offline Machine Notifications extension which is great but doesn't allow for HTML notifications. If that could be adjusted that would be a great start however there is so much power in your guys triggers. If there was a delay on something being triggered not only could you use this for offline machines but also you could delay cmds and have auto fixes through control. Hmm maybe even give Automate a run for it's money.
We also need this functionality for ScreenConnect Access session automations.
The current Session Event Automation system fires immediately when a Connected or Disconnected event occurs. This makes it difficult to create reliable offline monitoring because brief network interruptions generate unnecessary offline and online notifications.
The requested behaviour is:
Example:
This should be built into Session Event Automations rather than limited to the Offline Machine Notifications extension. Native automation support would allow the existing SMTP, webhook, Microsoft Teams, command, and other automation actions to be used.
Suggested implementation options:
$5MINUTESAGO$2HOURSAGO$7DAYSAGO$NOWSession.LastGuestDisconnectedEventTimeSession.LastGuestConnectedEventTimeSession.GuestOfflineDurationThis would reduce alert noise caused by brief internet interruptions, agent restarts, machine reboots, and ScreenConnect server restarts while still providing reliable notifications for genuine outages.
Search terms: delayed trigger, trigger timer, offline machine alert delay, reconnect notification, offline duration, Access guest disconnected, automation delay, debounce notification, suppress brief disconnects, relative time automation filter.
I see, makes sense now. The biggest thing here is just having the ability to delay triggers. Then you could really do a lot with this.
I have a nice HTML online alert for this as well. Set HTML as True and drop this code in body ;-)
I've got you on that one, create a new trigger servers online
Event Filter:
Event.EventType = 'Connected' AND Connection.ProcessType = 'Guest' AND Session.GuestOperatingSystemName LIKE '*server*' AND Session.HostConnectedCount = 0
Add as SMTP Mail
Subject:
Server Online
Body
{Session.Name} started responding at {Event.Time}
Glad this has been picked up! For us the best result would be just a simple text box where you can put in seconds before a trigger actually triggers (allow a different time for each created trigger).
So if I had 2 triggers one for "servers" and one for "clients" I could set a ~60 second timer for "servers" just to remove any internet blips and reboots and a ~300 second for "clients".
Im not sure if it's changed yet but the reason we don't use the extension was that it didn't include when a machine comes back online.
As a side note, my ticket was merged here and another large problem we have is if the Control server reboots it floods us with every machine coming online. Would it be possible to delay triggers on the Control Server all together for like 60 seconds while it settles from a reboot?
Please add the ability to have a delay option in your triggers! I use the Offline Machine Notifications extension which is great but doesn't allow for HTML notifications. If that could be adjusted that would be a great start however there is so much power in your guys triggers. If there was a delay on something being triggered not only could you use this for offline machines but also you could delay cmds and have auto fixes through control. Hmm maybe even give Automate a run for it's money.
for instance, if a server is offline for 30+ days, have an is activate a trigger event