If the clock is correct and changes as it should then this should work. However if for some reason the clock doesn't change, or if you're in a networked environment where all the rivendell workstation clocks are not sync'ed with the server, then I've run into issues - not related to time change, but related to when a workstation triggers an event versus the time the server has (particularly with rdcatch).
One option is to schedule the event for 1 to 2 seconds after the TOH, I've found that smooths out the RDCatch issues that I see occasionally. I imagine it should work for time change too. Lorne Tyndale > > > One of my clients had a timed event scheduled for 3:00 AM this morning, > that is, for the instant that 2 AM suddenly becomes 3 AM, and the event > did not fire. > > Does anyone know if this feature has ever been tested under these > conditions? > > > Rob > > -- > Я там, где ребята толковые, > Я там, где плакаты "Вперёд", > Где песни рабочие новые > Страна трудовая поёт.<hr>_______________________________________________ > Rivendell-dev mailing list > [email protected] > http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev _______________________________________________ Rivendell-dev mailing list [email protected] http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
