Replies: 2 comments 2 replies
-
Well, since I use CronSchedule it's possible to pass a timezone to each cronschedule like: |
Beta Was this translation helpful? Give feedback.
0 replies
-
No global setting no. This is the first time I hear about this behavior. Could it have something to do with the schema? Would be interesting to see if it could be reproduced in a test. There is an |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello kagkarlsson and community,
I've been using
db-scheduler
for task scheduling and have observed some behavior that I'd like to clarify.Current Setup:
Observed Issue: During the "Fall Back" DST transition, I noticed that tasks scheduled around the time switch can end up being scheduled for a time that's already passed.
For example, if a task finishes at 1:50 am and is set to execute every 15 minutes, it schedules itself for 1:05 am, which is in the past. This causes the task to execute immediately and continuously until the current time surpasses the DST switch.
Additional Information: I've looked into the
db-scheduler
code and noticed that theOracleJdbcCustomization
class uses the default behavior from theDefaultJdbcCustomization
class for storingInstant
values. I'm trying to determine if the observed DST issue is due to the behavior of the Oracle JDBC driver or if it's related to howdb-scheduler
handles or configures date-time values.Questions:
db-scheduler
's handling ofInstant
values?db-scheduler
to use UTC or Unix timestamps for storing the execution time to avoid such DST-related issues?Thank you in advance for clarification!
Beta Was this translation helpful? Give feedback.
All reactions