Trips and dispatch

The message names both ends: "This trip cannot move from 'x' to 'y' status". Check the table above and move through the intermediate status instead — a scheduled trip has to be assigned before it can start. If the message says the trip "has reached a final state", it is archived, and archived is permanent.

Editing the trip will not help either. The edit form refuses a status field with "Trip status can only be changed using the status action buttons", because status changes run guards and write an event that a plain save would skip.

Open the trip, set a scheduled start, save, and then schedule it. A trip with no planned start cannot be placed on a board or checked for conflicts, so this is the one field the draft to scheduled step insists on.

Assign a driver first, then run the status change. The same check runs again at start, so a trip that lost its driver after being assigned will refuse to start with the same message.

If the driver you want is not in the list, they may not be a driver-type user. The trip form rejects any user who is not a driver, with a message saying the selected person is not one.

Two things have to line up before a trip can run without a vehicle. Your plan has to include the vehicle-optional entitlement, and the Require vehicle setting has to be turned off. Until both are true, every trip needs a vehicle before it can be assigned or started.

If the setting is locked and cannot be turned off, the entitlement is not on your plan. Contact your administrator, who can see this on the plan page.

Origins are optional by default, so this only happens on tenants that have opted in. Either set an origin on the trip, or turn the setting off if your operation does not work from fixed pickup points.

Either set the vehicle back to active, swap the trip onto a different vehicle, or force the start. A forced start is accepted only with an override reason — without one you get a second refusal asking for it, and the reason is written into the trip’s event history.

Trip start mode has three settings. Manual means only a driver-initiated start is accepted and a geofence auto-start is refused. Automatic is the opposite: the trip is expected to start when the driver leaves the origin, and a manual start is refused. Both accepts either.

Change it at Customization → Operations → Trip lifecycle. Note that automatic start also needs an origin with coordinates, and rejects a start from more than 10 km away as a bad GPS fix.

The message lists the offending stops by number and status. Complete or skip each of them, then complete the trip. A stop counts as finished when it is departed, skipped, failed or cancelled — anything else blocks the trip.

Pause needs a pause reason from the supported list — a free-text value that is not one of them is rejected as invalid. Cancel needs a cancellation reason and fail needs a failure reason, both free text. Cancelling a draft trip is the one exception: drafts cancel without a reason.

This is intended, and it is not reversible by un-cancelling — a cancelled trip can only be archived. The skipped stops carry an automatic skip reason naming the trip status that caused it, so the history explains itself. If the work still needs doing, build a new trip for the remaining stops.

Refresh the trip and redo your change. Cooriroo versions every trip and rejects a write that carries a stale version, so two dispatchers editing the same trip cannot silently overwrite each other. On a busy trip this is common: the driver moving through stops bumps the version too.

Stops only move while the trip is en route or paused. If the trip is still assigned, or already completed, the message names the trip status rather than the stop. Otherwise the stop itself is departed, skipped, failed or cancelled, which is final.

A stop also has its own path: pending to en route, then approaching, arrived, servicing and departed. Skipping is allowed from most of them; marking a stop failed is only allowed once it is en route or servicing.

Departing a stop first auto-skips its optional tasks, then refuses if any required task is still unfulfilled — the message lists them. Complete them, or waive the proof, then depart.

Skipping is separate. Every skip needs a reason, and a stop marked as required can only be skipped by an admin, not by the driver in the app.

The four causes, in the order worth checking:

• Every stop is already finished. Routing only uses active stops, so a trip whose stops are all departed or skipped has nothing to draw.
• The trip has no route plan yet. Calculate a route before asking for its ETAs or deviation.
• Route preview needs at least two active stops; a full route calculation needs at least one.
• Maps are not configured for this environment, which reports the service as unavailable rather than as a validation error. That one is for your administrator.