Overview of Totalmail
TotalMail is a messaging system and a vital component in the line of communication between drivers and dispatchers. By using PeopleNet units installed in a driver’s tractor, TotalMail can send information about an order’s progress to TMW without having to be manually entered after a driver’s shift is over. A couple common errors that can occur in TotailMail are Messaging Sequencing Errors and Invalid Stops Errors. This document will address how to identify and fix these types of errors.
Message Sequencing Errors
Occasionally errors will occur in TotalMail, and these errors require dispatcher intervention to correct. One common error message that can appear in the TotalMail Inbox is ‘Message Sequencing Errors’.
How to Identify
An error message’s Error Information box will state that the driver:
“Attempted to update Stop #__ when a later stop already completed.”
What It Is
When a later stop in a trip is completed by a driver, before they complete an earlier stop, the system will automatically mark the skipped stop as completed for them. As is shown in the above example, if a driver submits a “Crude Delivery” at a station before they submit an “Arrival” at the station, TotalMail will automatically update TMW to consider the “Arrival” complete. If the driver then attempts to submit an “Arrival” at the station, the message will return an error that it cannot update already completed stops.
How to Resolve
In most cases, the message can just simply be deleted from the Inbox. If later stops by the driver are completing without error, there is not much gained by editing time stamps to fix the error message. Instead of resolving the message itself, view the driver’s TotalMail history folder, and examine it for other errors. If the driver repeatedly submits stops out of sequence, note the information, and contact the driver or their AOM to prevent these message errors from happening again.
Invalid Stops Errors
Another example of an error that can occur in a client’s TotalMail system is an Invalid Stops error. When this error occurs, a message will pop up in the client’s inbox. The following describes how to identify the error, what causes the error, and what to do to correct it.
How to Identify
A workflow message in the inbox will show an error, and the Error Information will state:
“Couldn’t find a valid stop.”
What It Is
This error is usually caused by a driver attempting to clear workflow off the unit. By submitting all the steps associated with a load at the same time, it will push the information off of his unit. Because TotalMail cannot properly interpret these empty messages, it will error them out.
How to Resolve
Due to the nature of these errors, they can be simply deleted from the Inbox. The company may want to make a note of the driver involved, as repeated blank messages may be a result of a larger problem. Drivers should be trained to properly submit workflow steps. This could avoid the same kind of error occurring in the future.