No, it sidled away, whining piteously.did it come back ?
😉
Patrick,
Thank you for your reply. My apologies for the delayed response, we have been receiving a large amount of incoming requests as of late. We had our informed our system administrators and they have re-synced the date/time on the web nodes so this should clear up the issue in the meantime. I apologize for any inconvenience this may have caused.
If you require any further assistance, please do not hesitate to contact us by replying to this support request, or by calling us at 310.841.5500. We are here 24/7 to assist you.
I had a few of those "Timing errors" last week. Just chaulked it up to no fire. I circled back on the thread few minutes later and done. That's the real life work around.Submitted another request -
It is bad this time - one of the nodes is out by 3 minutes.
What sucks is this is a simple set-up issue where - the node is not checking with the local time "leader" - which checks with the internet time server.
Hell, even my bedside clock syncs up using gps signals.
I'm not gunna make my 3rd quarter bonus because of this. 😉
we need you @Patrick. The space time continuum is broken again.
Wrong. I saw a few tagged "...in X minutes" over the past two days. Just tired of screen grabbing them when I didn't post in those threads anyway...
Wrong. I saw a few tagged "...in X minutes" over the past two days. Just tired of screen grabbing them when I didn't post in those threads anyway...
It's prolly because by now... you know that when the last post says "in a x minute/s"... you just don't hit that reply buttonugh - nothing in the error log. let me know please.
a little negative reinforcement to teach the community how to deal with adversity.
?
such a bummer getting the oops box.
I kinda unloaded on the last rep i got. He asked why I was referencing a "resolved" issue