Today our engineers noticed that the memos they create are going in with a timestamp an hour later than they are actually being submitted. We are EST, our cloud server says Central. If anything I would expect the time to be an hour behind. Could this be a daylight savings thing? Where can I look to change this so it shows the correct time for memos?
Here you can see an example where I reproduced the issue on a fake job.
Thank you!
Nate
What does the Ice.Memo table look like? Should be stored in UTC and give you an idea of whether it’s being converted incorrectly before entry into the database or after being retrieved.
Either way, you’d expect it to convert correctly. 
The Ice.Memo table shows the date/time as 7/1/26 1:19pm. The memo shows the date/time as 10:19am, and the memo was entered at 9:19am. 
My setup matches yours except the server time zone (eastern), and my conversions are working properly (-4 hour offset). Makes me think it might be using central when entering the timestamp for some reason.
Is your time zone also set on the site?
It’s EDT currently so UTC - 4 unless somewhere on the east coast recently Arizona’d.
09:19 EDT + 4 hours = 13:19 so it looks like the right UTC time is getting stored?
The conversion back is what’s borked.
Checking on our PDT instance, our memos are displaying minus one hour from actual. Checking the HTTP response, it’s on the backend so would be kind of annoying to fix from the client side.
It’s an old problem that keeps popping up in random places. If you’re in your server’s timezone, no problem. If you’re east, you gain an hour; west, you lose an hour. $5 says there’s an if east then + if west then - and they stuck a DST one hour modifier on the wrong side of the equation.
Super fun when this bug gets pasted into task schedule code and offsets the scheduled time one hour every day. At least memos can’t iterate?
