Troubleshooting ControlUp Scheduled Triggers

A user encountered a problem with a scheduled trigger in ControlUp. They questioned why it executed multiple times and needed advice regarding filtering, as well as the possibility of a timeframe limit. Another user suggested checking if the monitors were all running on time and taking timezones into account.

Read the entire ‘Troubleshooting ControlUp Scheduled Triggers’ thread below:

Hi guys, we have scheduled trigger assigned to Session to kill a process everyday at 3:30 am. today the trigger was executed multiple time on dozens of workstations at a later time. do you know how could it be? furthermore when you assigned scheduled trigger to session it will only executed on machines with sessions automatically or i need to do some filtering? in the screenshot you can see Error events saying that because there is no user logged on to session the action could not run. i thought that ControlUP would filter machines with no sessions. Thanks a lot in advance and have a good day.

make sure to username or name is * in the filter otherwise it also hits on system sessions

Thanks Wouter. i updated our triggers. any idea of the multiple execution of the action?

1 user and 1 or 2 system sessions. also check if all monitors run on time. be aware that this is always the local time of the monitor so if they have different times (zones) one monitor hets rebooted, machine gets assigned to a different monitor and comes to that time it might fire again

the time on monitors is correct. if the trigger was set to 3:30AM is there a timeframe limit that controlup works by?

Continue reading and comment on the thread ‘Troubleshooting ControlUp Scheduled Triggers’.  Not a member? Join Here!