Scheduler really simplifies things but there is a show-stopping bug in the Start Date field. This should be a TIMESTAMP(6) WITH TIMEZONE field but is being treated as a DATE. If a job has been defined with a timezone and is then edited, the timezone is discarded and it becomes a UTC -08:00 (for what was US/PACIFIC). Also, the calendar pop-up doesn't support time so if you use it, you lose the time a job is scheduled. These are a MAJOR problems because it means I cannot edit or set up jobs properly with this feature. Please fix ASAP. Thanks.
Scheduler Start Date Bug
- Thread starter kp4dan
- Start date
We'll check it out.
Stew Stryker
Member³
Did anything come of this? We just ran into this bug a few days ago. It seems people have been resetting the start date from the original values (that were defined via code to include time zones). Someone picked up that one of the jobs ran an hour early after last weekend's Daylight Savings Time change. It turned out that 20 out of our 30+ jobs didn't have a timestamp component, which tells Scheduler how to handle the DST change.
We've manually fixed these start dates, but that's going be a problem for us in the future if PSD doesn't automatically handle it.
Thanks,
Stew
We've manually fixed these start dates, but that's going be a problem for us in the future if PSD doesn't automatically handle it.
Thanks,
Stew
This is indeed a limitation at the moment. We will change this to a timestamp with timezone in an upcoming release.
Similar threads
