Errors
no_shift_coverage
No fleet shift covers the pickup time.
HTTP 422invalid_request_error
Your times are correct. Nobody works at that time.
Univooz compares the pickup time with the shifts the fleet has planned in the routed zone.
Why it happens
| Mode | Cause | param |
|---|---|---|
asap | No shift covers the pickup, and no shift starts within 240 minutes. | schedule |
deliver_by | Your deadline holds the pickup in place, so it cannot move to a shift. | schedule.time |
exact | Never. Univooz does not check exact times. | — |
Why 240 minutes. This is the zone horizon. Univooz can move an asap pickup to the
next shift, but not past the horizon. A collection many hours later is not useful to you.
Drivers. Inside the horizon, a shift must also have a driver. Outside the horizon, a planned shift is enough. So an order for next week is not rejected because the fleet did not select its drivers yet.
How to fix it
asap— try again later, or sendexacttimes.deliver_by— send a later deadline, or sendexacttimes.
If you get this error often, ask the fleet about its shifts. This is an operations problem, not a code problem.
Example response
{
"error": {
"type": "invalid_request_error",
"code": "no_shift_coverage",
"message": "No fleet shift covers the requested pickup window.",
"param": "schedule",
"doc_url": "https://docs.univooz.com/errors/no_shift_coverage",
"request_id": "req_01KZCCF8ZH4M7XQ2VB9RSTNPKD"
}
}