You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
i thought about filing this as a bug, but i'm afraid i'm not using the latest version (still on v7)
i just noticed that our server (UTC zone) was running jobs 1 hour early (jobs scheduled in America/Vancouver zone) after the clocks changed this weekend.
once i restarted the jobs, they went back to being scheduled at the correct time of day.
i saw no mention of this as a bug or fix, so i have not upgraded to see if this bug remains (or maybe bug is too harsh - a limitation?)
anyway, i think what i will do for myself is kill of the job process once a week to avoid this, but i think this should probably be mentioned in the documentation (if it has, my bad!)
anyway, since i mentioned this as Q&A, is this still an issue with the latest version?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
i thought about filing this as a bug, but i'm afraid i'm not using the latest version (still on v7)
i just noticed that our server (UTC zone) was running jobs 1 hour early (jobs scheduled in America/Vancouver zone) after the clocks changed this weekend.
once i restarted the jobs, they went back to being scheduled at the correct time of day.
i saw no mention of this as a bug or fix, so i have not upgraded to see if this bug remains (or maybe bug is too harsh - a limitation?)
anyway, i think what i will do for myself is kill of the job process once a week to avoid this, but i think this should probably be mentioned in the documentation (if it has, my bad!)
anyway, since i mentioned this as Q&A, is this still an issue with the latest version?
Beta Was this translation helpful? Give feedback.
All reactions