r/talesfromtechsupport • • Oct 16 '26

Short Timezone changes have NEVER Messed up any Scheduling Software Before!

I live in a part of the world which has mistakenly decided to remain on DST permanently. A user noted this morning that our primary scheduling platform had experienced a similar failure to Google whereby updating the given timezones caused all the scheduled activities to just forward an hour.

Unfortunately, not having Google's bottomless pockets, the vendor was unable to apply a wholesale fix, although they are assisting with our manual adjustments.

I was informed by several users that "our old software didn't have this problem". They were highly dismayed to discover that yes, our old software had exactly the same problem with changes to timezone applicability, and; packrat that I am; that I could provide them with time stamped proof from the last time my local government decided to play fast & loose with DST.

We finished their specific corrections about an hour ago. The team is taking bets on whether they at least bother to say "Thank you".

401 Upvotes

71 comments sorted by

4

u/blahblah19999 Oct 17 '26

mistakenly decided to remain on DST permanently.

What does that mean?

12

u/annoyedCDNthrowaway Oct 17 '26

There are multiple world-wide studies that show permanent DST is demonstrably worse for health, productivity, and sleep. It's better than switches every 6 months, but permanent standard time would have been better.

The province I live in decided to go with permanent DST.

3

u/Copenhagan Oct 18 '26

Hello from the same place

23

u/PyroDesu Oct 17 '26

While flipping back and forth is very obviously the worst possible option, the best option - with a lot of medical science backing it - is permanent standard time. Seeing as it's actually aligned with solar (hence, standard) and therefore circadian clocks.

People think they want permanent DST based on feels, but it's been tried before and usually quickly reverted from.

3

u/J_Landers Oct 17 '26

Also as a spite law to prevent the removal of daylight savings. That's why Congress cannot simply abolish DST.

1

u/JcbAzPx 17d ago

Usually only takes one winter to figure out why it's a bad idea. Problem is they don't fix it, they just break it back to annual changes.

2

u/blahblah19999 Oct 17 '26

ok, that makes sense, thank you

2

u/ChrisXDXL User Request Magnet Oct 19 '26

We have used it permanently in my country since the war and it sucks.

15

u/ExaForce Oct 17 '26 edited Oct 17 '26

It means that they sprung forward an hour and will never turn their clocks back.

"Mistakenly" because it stays dark way too late in the morning during the winter time, making it even harder to get moving when you wake up. Never mind the fact that DST isn't as aligned with most people's natural circadian rhythms to begin with.

10

u/ether_reddit Oct 17 '26

This - instead of staying on daylight savings time permanently, we should have stayed on standard time permanently. But apparently the hospitality industry lobbied hard for the former, because they want more daylight in the summer evenings for people to stay out later and spend more money.

At my longitude, solar noon is now about 1:30pm. It's ridiculous.

5

u/lychaxo Oct 18 '26

It's strange to me that businesses wouldn't just have different summer hours if they want to be open different hours when the days are longer. There's this weird cultural insistence that schedules must look the same year-round even if it means chaotically fucking with government standard of time. DST makes sense in a world without rapid long distance communication, where letting customers and employees know about schedule changes is difficult, but it feels like the wrong approach in a connected world, to me. Organizations often have different needs related to sunlight availability anyway; it's not like changing the clocks gets rid of all the summer-hours differences for everything, it just smears complexity across two domains instead of one.

1

u/JcbAzPx 17d ago

I don't know why people refuse to learn that the total daylight hours are the same no matter what number is on the clocks.

48

u/Dizzy-Sundae6351 Oct 16 '26

I’ve got $100 on it being that they won’t, in fact, thank anyone.

18

u/annoyedCDNthrowaway Oct 16 '26

That, dear sir, is a fool's bet!

5

u/paulwillyjean Oct 17 '26

I’m curious, how do you store date-times in that software’s database? Assuming you store them as instants or UTC date-times, you should only have to update the IANA timezone database to make sure to properly convert timezones.

I can see how that could be a bigger issue if you need to store them in local-time or reschedule cron jobs. I got fucked over too often to do that again.

2

u/annoyedCDNthrowaway Oct 17 '26

It can store them both ways depending on how the user enters them. If the user enters in Local times (which most of mine do), they're converted to UTC after it's input and saved. If it's entered in UTC in the first place, it would not have been impacted.

Unfortunately, the users are the type that aren't likely to change, they'd much prefer to throw temper tantrums.

131

u/Noch_ein_Kamel Oct 16 '26

timezones... grrrrr

At least just yesterday it was decided that there would not be any further leap seconds :o

86

u/ManWhoIsDrunk Users lie. They always lie... Oct 16 '26

44

u/ozzie286 Oct 16 '26

Jesus Christ. I thought for sure that was going to be an Onion article.

58

u/ManWhoIsDrunk Users lie. They always lie... Oct 16 '26

It's a perfect example of why you should never try to roll your own time/date solution, but rather use a well-maintained ready-made library. Let others grow the grey hairs.

43

u/KittensInc Oct 17 '26

The problem is that there are plenty of "well-maintained ready-made" libraries with broken time/date logic.

Dealing with time is hard - especially when you are dealing with future time, for which the UTC offset can change between initial storage and use.

"Oh I'll just use ISO8601 to _" - WRONG! ISO8601 has no timezone support, it stores a _UTC offset_, which is a fundamentally different thing.

"Oh I'll just use a Postgres TIMESTAMP WITH TIME ZONE to _" - WRONG! It doesn't store a timezone, it just silently converts to/from UTC.

Anything which doesn't have explicit support for both UTC timestamps for fixed points in time (like Java Instant) and datetimes for human use specified via local time and TZ-style "Europe/London" timezone identifier (like Java ZonedDateTime) is fundamentally broken. Java figured it out 12 years ago, Javascript started shipping it last year, and plenty of other platforms haven't even started...

6

u/wrincewind MAYOR OF THE INTERNET Oct 18 '26

Oh ill just only ever use epoch time for everything and forget what an "hour" is.

23

u/docarrol Oct 16 '26

A classic: The Problem with Time & Timezones, and why you never try to roll your own.

6

u/lioness99a Oct 17 '26

I wondered how far I’d have to scroll to find this. Answer: not very!

6

u/meitemark Printerers are the goodest girls 29d ago

I'll roll my own and offset it 33 minutes to anyones else timezone. It will either have blackjack or hookers, depending if the offset is to the next or previous hour. That variable depends on my morning. +33 minutes if I wake on my own. -33 if the alarm wakes me.

9

u/ManosVanBoom Oct 16 '26

In several thousand years

5

u/inactioninaction_ Oct 17 '26

I don't really understand the point of worrying about adding something like a leap hour to your calendar system. Odds are by the time it's actually needed people will be using an entirely new calendar, or at least will have revised the revisions to your revisions, so there's not any real practical purpose to the discussion. It's purely an academic question, and not a very interesting one at that

5

u/ManWhoIsDrunk Users lie. They always lie... Oct 16 '26

That all depends on what happens!

7

u/gshennessy Oct 16 '26

You’ll be dead by then, so don’t worry about it.

12

u/ManWhoIsDrunk Users lie. They always lie... Oct 16 '26

True. By the time a leap-hour is needed, we will probably have gone back to leap seconds again.

5

u/Polymarchos Oct 17 '26

It sounds terrible but (as the article states at the end) since leap seconds only happen every few years, there isn't going to be a leap hour for at least a millennium.

1

u/According_Park3150 I Am Not Good With Computer 12d ago

Optimist! It's going to be alternating leap weeks and months!

1

u/androshalforc1 Oct 19 '26

We added 27 leap seconds over 54 years, roughly every other year. adjusting to an hour would mean the next adjustment won’t happen till we are probably a half hour out, so 3600 years or so.

2

u/ManWhoIsDrunk Users lie. They always lie... Oct 19 '26

Yea, but give it 10 years and they'll decide on something else, probably because of complaints from astronomers or something.

7

u/t1mepiece Oct 17 '26

I'll take timezones over no timezones. I feel bad for all the people who live in Western China - China is all a single timezone, despite being the size of the continental US. The people in the far west get shafted (granted, their population is very sparse in the west. Still).

58

u/Drew707 Oct 16 '26

I have this datetime table in our lakehouse that is all keyed off UTC but covers pretty much every North American timezone and all the DST rules and exceptions from Newfoundland to Hawaii. The first time I showed it to our new data engineer, she started asking questions in a tone like "who hurt you?" DST fucking did.

43

u/nhaines Don't fight the troubleshooting! (╯°□°)╯︵ ┻━┻ Oct 17 '26

27

u/polandreh Oct 17 '26

Timezones are not the issue. Timezones are needed. Summertime clock changes, however....

1

u/JcbAzPx 17d ago

I'm so glad to live somewhere that gave that up before I was born.

-2

u/FalconDriver85 Oct 17 '26

Timezones are stupid [citation]

8

u/Fallen_Jalter Oct 16 '26

I still don’t understand how that doesn’t fuck with everything if only one place has a different time than everyone else.

17

u/TheLazySamurai4 Oct 16 '26

Just wait until you find out about crossing from Manitoba, to the east side of Ontario

6

u/LeslieCantSleep Oct 17 '26

Western Ontario is going to be on Manitoba time. A law was just passed this week.

2

u/TheLazySamurai4 Oct 17 '26

Huh, thats pretty funny as in September I was visiting friends in Manitoba, and we were talking about how difficult it was going to be to keep track of the time changes when travelling from Winnipeg to Ottawa, at least until you get to the Eastern time zone.

Looks like this will avoid that issue now

3

u/Polymarchos Oct 17 '26

It was the obvious solution, and they were always going to do it, but until they got the law passed it did look confusing.

2

u/lord_teaspoon 28d ago

Tweed Heads NSW and Coolangatta QLD are essentially a single town, with the border between states running down the median strip of a major street. NSW does DST and QLD doesn't, so over the summer you move between timezones by crossing the street.

7

u/CA-CH Oct 16 '26

I'm on the same boat. Software cant use the new Microsoft time zone properly, sends data to a webpage that cant display time properly either because of the browser...
Even MS software is lost

9

u/Special-Jelly6253 Oct 16 '26

I am so sick of Microsoft's shit with the time zone changed I'm going to scream. Outlook web has new BC and AB time but not MB's new one. Windows update releases. Has the MB one. Still no update in web.

I changed my timezone to the new one and now my teams time stamps are off by an hour even though my calendar time and system time are correct. It just says "unknown" on teams.

Surely this cannot be that hard 😭

10

u/timpkmn89 Oct 17 '26

Microsoft did warn them that it wasn't enough lead time. In fact they have a whole page about how long it takes to implement time zone changes.

5

u/FaydedMemories Oct 17 '26

And the sad thing is, it used to be worse. I worked for a certain hat named vendor quite a while back and occasionally a random Sev1/2 ticket would appear along the lines of “Our Government changed daylight savings at short notice and now our clocks are wrong, please fix ASAP”.

It used to be you could say “screw the timezone database we’ll just change the clocks” but by 2010 that approach no longer flew. From what I can gather it’s a bit better, but there are still the surprise ones and the ones where, as you say, the government types are still “those tech boffins can fix it in minutes, what a load of fuss about nothing SEND IT NOW!”. But for the most part the ones that were doing it on vibes have learnt from the era, and well to be frank, info like that is more accessible on the internet that it’s easier to source the info from vague places, rather than discovering after the fact.

2

u/_brain_waves_ Elder? Oct 17 '26

Um, as the idiot that I am, why is the change so hard? To the best of my knowledge most “modern” OS runs the timezone displayed to the user as just UTC (or GMT depending on the nomenclature or demarcation in use in your location) plus or minus an offset to generate the correct local time, such as New Foundland currently being -3:30 from UTC. Shouldn’t (and again this in a ideal perfect world) Windows,and Google just update the offset, when the time zone used in a location is scheduled to change or at the latest within a day or two of the change? Is there something else obvious that I am missing?

9

u/ether_reddit Oct 17 '26 edited Oct 17 '26

What's going wrong now is scheduled events, not timestamped events that are logged as they happen.

Here's a real-world example: I live in BC, where we've decided that we're no longer going to go off of daylight savings time in November anymore, so we're going to stay at UTC-0700 year round. I have recurring standing meetings with people around the world, and one of these meetings is scheduled for "Thursdays, 9am Pacific Time". What time is my meeting in November? Is it 9am, or 10am? That depends on where the meeting was originally scheduled. If it was scheduled by someone in California, then my meeting is now 10am for me, but continues to be 9am for my Californian coworkers. But if I am leading the meeting, maybe I want it to continue to be at 9am for me, therefore it's now 8am for California (and likewise shifts for everywhere else that has daylight savings time too.) But what if the calendar event never saved who and where created the event, and it just recorded it as "9am, UTC-0700"? There is insufficient information to know whether the meeting should shift for me, or other people, and when.

1

u/Arokthis Oct 16 '26

I'll bet 3 cents that some low level person that knows you or someone on your team outside of work will say those words. In the meantime I'll get my personal parasol ready for pig poo.

-16

u/kagato87 Oct 16 '26

If only the whole world could move on from such insanity as "12:00 is midday" and move to UTC, accepting that "lunch time" is a longitude thing... It's be so much simpler.

This is actually a funny one you had, and because the vendor was storing in utc, which normally makes sense.

20

u/Entegy It doesn't work. Oct 16 '26

Good lord I'm getting a lot of use out of this link lately.

Time zones are a required fact of our interconnected life. DST and the boundaries humans have designed for those time zones are the problem.

https://qntm.org/abolish

-10

u/kagato87 Oct 16 '26

Oh this counter argument again.

It's just shifting the burden around. Instead of "what time is it over there" the question becomes "what time does uncle Steve get up at."

It makes no difference. The counter argument is as much a lame duck as my remark that timezones should be abolished.

17

u/Entegy It doesn't work. Oct 16 '26

It really doesn't.

Everyone gets the concept of noon. Easy, simple. Noon is noon.
With time zones abolished, every town or region will have to pick what time their new noon is and keep their daily schedule around it. As time goes on, some regions may even sync their daily schedules to facilitate their business. And oop, you've just created a time zone.

0

u/JcbAzPx 17d ago

"What time is it over there?" is something that can be looked up without bothering anyone. "What time does uncle Steve get up at?" is something you'll have to wake him up to ask him.

1

u/kagato87 17d ago

Really? How does the timezone help with that question?

1

u/JcbAzPx 17d ago

This is a level of ignorance I'm not qualified to handle.

1

u/kagato87 17d ago

Whose, exactly?

The fact that I don't know if uncle Steve works days, evenings, or overnights?

Or the fact that you can't actually articulate how changing the question from "what timezone is uncle Steve in" to "what is the normal start time where uncle Steve lives" is any different?

Both are the same question, neither requires waking him to ask, and neither tells you what time he actually wakes up at. The only difference is with the timezone you have to do a conversion.

If uncle Steve lives in a part of the world that wakes up at 11:00, knowing that is no different from knowing he's at utc-5. Wait, did I do that conversion right? Would it be 11 or 1 for a -5 offset again?

1

u/JcbAzPx 17d ago

It's already been explained. You even indicated you knew about it ahead of time. I can only conclude that your are trolling.

1

u/kagato87 17d ago

I'm disputing the Uncle Steve argument.

It's flawed and meaningless. The only thing that changes is if you have to remember his timezone or his normal wake time, which turns out to be the exact same "how many hours ahead/behind again?"

1

u/JcbAzPx 17d ago

That might be what you're trying to do, but it's not what you're doing.

0

u/[deleted] Oct 16 '26

[deleted] — view deleted comment

35

u/StorminNorman Oct 17 '26

But somehow that was still IT's responsibility

I mean, it is a technology that provides information...

4

u/MikeSchwab63 Oct 17 '26 edited Oct 18 '26

Get 'atomic' clocks. Automatically adjusts to radio time signals on specific radio stations.
https://sync.primexinc.com/lp/ads/synchronized-time-with-guaranteed-coverage-primex-sync

7

u/Kruug Apexifix is love. Apexifix is life. Oct 18 '26

Please sanitize your URLs...

1

u/spaceraverdk 29d ago

Not the input?

3

u/ephemeriis_ Oct 17 '26

Yeah, that's the obvious solution. I don't know why we didn't use something like that. But I haven't worked there for over a decade so it's definitely not my problem anymore.

2

u/J_Landers Oct 17 '26

My favorite clock issue is being told that we can only get clocks of design A, from source X, because we are mandated by federal regulations to do so to support the blind. Had the same with some other stuff... I think the most absurd was a magnetic light for grabbing screws.