This article helps to understand why a driver may not appear in a mission or DTR.
Purpose of the article
Identify the checks to be made when the expected driver is not visible.
Possible causes
- No drivers have yet been assigned.
- The driver has not yet been traced by the source.
- Synchronization is pending.
- The driver is not linked to the correct record or status.
Screenshot to insert: driverless mission screen displayed.
Checks to be made
- Verify that a driver has been assigned.
- Check the status of the mission or DTR.
- Check synchronization between interfaces.
- Make sure the driver is assigned to the correct route or lot.
What to do next?
- If the driver is not assigned, make the assignment.
- If the ascent is late, give time for synchronization.
- If the driver remains absent, contact support.
In summary
- The absence of a driver often comes from a missing assignment or a synchronization delay.
- First check the assignment and status of the file.
Need help?
If the driver is still not displayed, contact support via support@waynium.com with the mission reference and the identity of the driver.
Comments
0 comments
Please sign in to leave a comment.