Assigned
Status Update
Comments
bl...@google.com <bl...@google.com>
gi...@google.com <gi...@google.com>
ta...@swc.co.il <ta...@swc.co.il> #2
+1
fa...@windtre.it <fa...@windtre.it> #3
+1
sh...@google.com <sh...@google.com>
bw...@google.com <bw...@google.com> #4
Thanks for the feedback. We will consider for our roadmap.
bw...@google.com <bw...@google.com>
[Deleted User] <[Deleted User]> #5
We are still having the exact same issue.
The scheduled query was an hour's late after the winter time started and we will have to modify our time-sensitive queries twice a year... Please fix this issue. We are hoping the scheduled query time will be changed automatically as summer time starts/ends.
Thanks!
The scheduled query was an hour's late after the winter time started and we will have to modify our time-sensitive queries twice a year... Please fix this issue. We are hoping the scheduled query time will be changed automatically as summer time starts/ends.
Thanks!
rn...@gmail.com <rn...@gmail.com> #6
I wish we could just schedule in UTC....this time zone selection has ruined scheduled jobs in BQ UI
[Deleted User] <[Deleted User]> #7
I have had the same issue with a query running 1 hour later than expected after the recent change to BST (UTC+1).
iv...@autoscout24.com <iv...@autoscout24.com> #8
We have the same issue - schedules just run 1 hr later on CET time and the change in the BQ UI is not able to overwrite it. This is frustrating. Thanks!
jo...@meermetdata.nl <jo...@meermetdata.nl> #9
Same issue here, scheduled time stays CEST instead of CET. So refresh is an hour early.
di...@gmail.com <di...@gmail.com> #10
I'm still having this problem. Is there any workaround?
ra...@kinesso.com <ra...@kinesso.com> #11
Still having the same issue. Is there any news about it?
ma...@emap.com <ma...@emap.com> #12
Hello,
Is there an update to this ticket or a work around for this issue.
Thanks
Is there an update to this ticket or a work around for this issue.
Thanks
ta...@gmail.com <ta...@gmail.com> #13
Any update on this issue, everytime day light savings change, have to updated the scheduled queries. this is frustrating.
mi...@brightspeed.com <mi...@brightspeed.com> #14
Is there any update on this? We are in production with many scheduled queries and this is a huge pain and causes production issues. This bug has been sitting here for years I cannot believe this has not been fixed yet. I have never heard of any job scheduler changing the timing of your jobs
ce...@google.com <ce...@google.com> #15
Is there any update on this? Our customer has the same question about Data Fusion.
Description
Problem you have encountered:
All my scheduled queries now run 1 hour later, because time has been changed to summer time (+1 hour) in my timezone. I've set the time after France, but apparently it is only calculated from UTC timezone. That's very unhelpful, because that means that I have to change all my queries every 6 months.
What you expected to happen:
If I choose the timezone France, then it should always run the queries according to the time I set in this timezone. E.g., 7:30 AM should always be 7:30 AM in my chosen timezone.
Steps to reproduce:
1. Set scheduled query to run at 7:30 AM France timezone (UTC +1).
2. France changes to summer time (UTC +2).
3. Query now runs at 8:30 AM France timezone (UTC +2).
Other information (workarounds you have tried, documentation consulted, etc):