I need to be clarified as how "Action depends on bad on" should be considere to Work:
Setup:
While having a test-Schedule of 24/7, I have created Action profiles that uses different time-restriction schedules for "bad" status actions.
For example, I do not want to send a "Bad" Send mail-action between 3am-5am, as this is considered a "planned reboot-window" so I have restricted the "Bad"-action with corresponding schedule. To still get alerted, if the tested unit has not got back online when the reboot-window ends, I have also selected "Deferred action". This setup works OK.
No "bad" is triggered between 3am-5am, but if unit does not come back online, I will be alerted at 5am.
In the "Good status-action" I also have a "Good" Send-mail action, for notification on OK-status in case of failures during daytime. However, I do not want to get notified when the unit have been rebooted in reboot-window, and starts responding Again.
So I have selected "Action depeds on bad one", as Hostmon has not send a "bad" due to the time-restrictions..(?!)
But... that does not seem to be how it actually works.. I still receive a "Good" email, when the unit get back online, inside the defined reboot-window.
Is this as expected?
Should I also apply a time restriction for the "good"-action to avoid getting the mail send?
What then, if I want to get the "Good"-action triggered, if the unit went "bad" before the reboot-window, but get back online inside it? Here I do wish to get the "Good"-alert...
I do not wish to restrict the tests by a test-Schedule, as we use the web interface as 24/7 status-display...
In fact, I have just re-configured all our 4900 tests, from using test-Schedules, to be using time-restrictions in "bad"-actions, for that very same reason.. :p
Hope I have described my challenge good enough...

Best Regards
Mikael K