Step 1: Search trip ID and open device health.
Step 2: Search the trip ID and then input double inverted comma to find the trip UUID. Copy the trip UUID and search the same.
Step 3: Search by "Trip started uuid =" Followed by the trip UUID.
Example: Trip started uuid = 4bbe02f8-f17f-793a-95e7-0096208d1901
Step 4: Check the previous logs from the trip start event log to understand how the trip was started.
A trip can be started by below 3 methods:
- First employee sign in (adhoc or planned any).
- Pressing the start trip button in shuttle trips.
- Synchronous duty/trip start command (this is a configurable feature and only works for shuttle trips).
Step 5: Search the recent logs for the trip UUID searched to find out the trip end reason.
If a trip is ended by signinng off all employees the you will find a log as "trip is completed because of employee sign off. Trip UUID:" followed by the trip UUID.
If a trip is ended via auto sign off then you will get a log as "trip is completed on reaching office. Trip UUID:" followed by the trip UUID as given in the example below.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article