I setup a trigger that will send an email notification when a VisualCron server has been turned OFF and another for when it is turned ON.
The OFF notification is working fine, but the ON notification only works if you do not reboot the system.

Here is the way we are trying to use this:
We turn the server VisualCron OFF, we get a notice letting everyone know that someone turned it OFF.
Then we reboot the system after updates or whatever. After the system comes back up, we turn VisualCron back ON.

The ON action is not triggering the notification.

I have the ON and OFF triggers set to ignore server OFF and the polling is set to 5 seconds.
The reason I have this set so frequent is because the end user would have to wait for the polling length in order for the notification to go out.

Your help would be appreciated.

Thanks

Here is a quick video demonstrating our settings. As you can see we have checked both server On and Off. Interval does not matter as this is instant always. If you look at the Last Run you will see that it reacts both to On and Off:

http://screencast.com/t/GNGBgnIq3Euc 

---

Have you tried turning off, rebooting, and then turning it back on after the system comes back up?
It does not send any notifications when I turn it on after reboot.

I can turn it on and off without rebooting and it works fine..

I think the problem might be that you have not checked "Ignore Server Off" in the Trigger. This specific setting and this specific Trigger require that the Trigger is active at the moment it Triggers. If you have Server Off then it is not active -- unless checking "Ignore Server Off".

---

Quote from my initial post:
"I have the ON and OFF triggers set to ignore server OFF and the polling is set to 5 seconds."

I found that if I wait long enough after the reboot, the server ON trigger works correctly.
If VisualCron prevents the turning on of the server until it is ready to process the trigger/action related item, then this issue goes away.

I found that if I wait long enough after the reboot, the server ON trigger works correctly.
If VisualCron prevents the turning on of the server until it is ready to process the trigger/action related item, then this issue goes away.

Yes, it might take longer than expected because:

1. system boots up
2. VisualCron service starts
3. VisualCron is doing general startup activities
4. This Trigger is triggered

---