Incorrect Message Time Reporting
See original GitHub issueScreenshots
Version
Webchat CDN v4.6/latest
Browsers
Edge v44.18362.387.0 IE v11.418.18362.0 Firefox v70.0 Chrome v78.0.3904.87
Describe the bug
The message reported timing is not showing correctly.
To Reproduce
Steps to reproduce the behavior:
- Run the webchat.
- Make conversation history.
- Wait around 5 min (longer you wait grater would be the inconsistency).
- See the reported message time inconsistency.
Expected behavior
The earlier entered messages should have grater reporting time.
[Bug]
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:11 (8 by maintainers)
Top Results From Across the Web
What to Say to an Employee Who Falsifies Their Time Card
How do you confront a worker whom you suspect has been falsifying time card data? What do you say to them? Confrontation can...
Read more >The Sent time stamp on email messages is incorrect in ...
The Sent time stamp on email messages may be incorrect when you sign in to Outlook on the web (formally known as Microsoft...
Read more >Wrong time on incoming texts | T-Mobile Community
The phone time is correct, the time zone is correct, and my outgoing messages have the correct time, only the incoming texts are...
Read more >COMMON ERRORS IN KRONOS AND HOW TO FIX THEM
Incorrectly reporting leave time. Leave time must be reported using the Pay Code field in Kronos. Employees may use the comments feature to...
Read more >Why do my incoming texts have the wrong time?
It actively corrects all timestamps to the correct time zone so that all SMS messages will be received as they should. 0. Comment...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This is the root cause. In Chrome:
The code above can sometimes print 99, instead of >= 100. And this is causing the timer not to be rescheduled, because the new scheduled time has not changed.
@arman-g This is scheduled for our next release. Updates will be posted here!