The issues you see in the monitor appear in the order by the date and time stamp they uploaded to the server, not by the date and time when they were created.
This is by design to allow you to see all issues as they arrive in the live monitor. Unfortunately, even with today's technology, outages or connectivity issues do occur. When there is a delay or interruption of uploading any issues, the device will hold the delayed issues until connectivity is reestablished,.
When the connection is reestablished, the issue(s) will then upload to the Silvertrac server and are assigned an issue ID. If the delayed issue(s) were uploaded to the Issue Monitor by date or time, the monitoring user would most likely never see the issues(s) as they would upload to a previous page.
NOTE: The actual date and time shown is the actual date and time the issue was created. If you are experiencing multiple date and time issues out of order in your issue monitor, we recommend investigating the connectivity issues related to the area your device is operating in?
The Issue History Report
You can run an Issue History report. This is an excel spreadsheet which will show both the date and time stamp of when an issue was created and then when the issue uploaded to the server.
It typically takes 30-60 seconds for an issue with photos, notes or audio files to upload to the server. The Issue History report displays any server time delays in minutes. With good internet connection the delay should be 0 or 1. In this example the server upload times were interrupted with a poor or no internet connection:
As an extra measure, Silvertrac has added a notification indicator "Uploads" at the bottom of the device users main screen. If there is an issue with the uploading created issues, the device user should always look at this area in the lower portion on the device screen and verify that they are all at zero.
If there are Issues, Messages, Photos or Audio files pending upload, the user should get to an area of good confirmed connectivity. These pending uploads should then start to upload.