Possible SystemDate Issue #45
Description
We have one report - only - of a user (in the UK) where the SystemDate call is coming back as something bizarre. We can't reproduce the issue locally (North America) but it's 100% reproducible for this one client. It doesn't seem to be a US/UK format thing.
Here's a concrete example:
Application time = 2017-02-16 08:57:01
System time call = 2016-09-13 14:39:01
The difference isn't always the same time-span; in this case it's -155:18:18:0 (d/h/m/s). (We're using SystemDate to calculate a time-zone offset, btw.)
I've tried to find a pattern to the error but so far it's escaped me. Any ideas? I see no other mention of this in Issues, open or closed, so I'm not sure if it's the wrapper, the API itself, a CM data center issue, or possibly own own code somewhere.