Trip is Not Sent to the Driver

Condition

A trip should have been sent to the mobile computer but does not appear to have been sent.

Cause

A number of possible causes exist for this issue.

Remedy

In Schedule Editor, find the run and check its Send status. If it shows DM, then check the Tracker Action Log to see if it indicates that the MDT Server or a user changed it to DM.

If a user changed it to DM, then the MDT Server would not have sent the event because it was marked DM manually. The user needs to be informed not to manually select the event as DM.

If it indicates DM by MDT Server, then the logs need to be checked by a system administrator to see if the MDT Server did send the event and received an acknowledgement.

If the event shows an ellipsis (...), then the system may not have tried to send it at all. This could be due to many reasons. The most common reason may be that the mobile computer was already at critical capacity.