Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Possible SystemDate Issue #45

Open
protegesolutions opened this issue Feb 16, 2017 · 0 comments
Open

Possible SystemDate Issue #45

protegesolutions opened this issue Feb 16, 2017 · 0 comments

Comments

@protegesolutions
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant