Wrong timestamp

[#1]

---

@JonoH wrote:

That's raised and I've had a little fun with it as well  

Wait a minute Khrous, uh, are you telling me you built a time machine?

You've spelt Lithium Khoros wrong.

@Townman wrote:

@Gandalf has learnt to bend light

I'm that good. 

if support can find out what bit of the service he was connected to just before midnight it might help them focus their investigations...

Fingers crossed their investigation finds the cause for the issue.

[#2]

---

@JonoH wrote:

That's raised and I've had a little fun with it as well  

Wait a minute Khrous, uh, are you telling me you built a time machine?

Has the response from Lithium been caught up in the time warp @JonoH 

Not seen any examples recently, but then I don't check the message timestamps that frequently.

[#3]

I got this on Monday

After investigation, I have found that this is a result of a bug. I have raised a request with the engineering team and they will be working on further investigation and fixing it.

[#4]

Still happening -

Message #17 here: https://community.plus.net/t5/General-Chat/Have-you-heard-the-one-about/m-p/1651868#M259003

And this post, edited at 11:52 pm on 30th June.

[#5]

---

@198kHz wrote:

Still happening -

As I posted above, we're aware of this issue and the bug that causes it, I'll let you know when it's resolved. 

[#6]

This bug fix has been added to version 19.7 of the Community. As we've just updated to 19.5 it may take some time before it's resolved for us.