Dispatch Failure Reasons

Category

Typical message wording

Error code displayed

Retry automatically?

What to do

Coverage

"Delivery address is outside the serviceable area" / "Pickup location is not in a supported market" / "No coverage for this region"

is ineligible because of location coverage: pickup_country=IE and dropoff_country=IE.

No

Confirm the pickup and dropoff addresses are correct. If they are, this location genuinely isn't served by that provider right now, try a different provider if one is available.

Distance

"Delivery distance exceeds maximum allowed" / "Dropoff is too far from pickup (X mi > Y mi limit)"

{"code":"address_undeliverable","message":"The specified location is not in a deliverable area.","kind":"error", "metadata":{"details":"The dropoff location is outside the delivery radius of the pickup location (Max Radius: X miles...)"}}

No

Double-check the pickup and dropoff addresses are what you expect. If they are, the trip is simply too far for this provider's limits, try another provider.

Hours

"Store is closed at the requested pickup time" / "Requested time is outside operating hours" / "Merchant is not currently open"

None — no code family, text only.

No

Check two separate things, because the message won't tell you which one is the problem: (1) the provider's market operating hours, and (2) your own store's set hours for that location. Fix whichever is wrong, or move the pickup time into an open window.

Lead time

Too soon: "Pickup time is too soon" / "Requested pickup is before the minimum lead time." Too far out: no error message appears at all.

{"code":"pickup_ready_too_early","message":"The pickup ready time cannot be in the past.","kind":"error"}

N/A

If an order looks stuck with no error message, don't assume it failed silently — it may just be sitting in planned_selection waiting for its booking window to open. If the message says pickup is too soon, delay the requested time.

Capacity

"No couriers available at this time" / "No drivers available in your area" / "Service temporarily unavailable in this market"

{"code":"address_undeliverable_limited_couriers","message":"The specified location is not in a deliverable area at this time because all couriers are currently busy.","kind":"error"}

Yes

Retry the quote after a short wait before treating this as a real failure.

Package limits

"Package exceeds maximum weight" / "Order value exceeds the allowed limit" / "Item dimensions are not supported"

{"code":"invalid_params","message":"the parameters of your request were invalid.","kind":"error","metadata":{"param_details":"total volume exceeds the limit: actual is 2274300 cubic centimetres, max supported is 2118912 cubic centimetres"}}

No

Check the order's weight, dimensions, and total value against the provider's published limits. If it's over, split the order, choose a different provider, or arrange delivery another way.

Vehicle class

"Requested vehicle type is not available" / "No couriers with the required vehicle in this area"

"errors":[{"detail":"cannot be over 350 ft³","source":{"pointer":"total_volume"},"title":"invalid value"},{"detail":"can't be blank","source":{"pointer":"vehicle_class"},"title":"invalid value"}],"message":"total volume cannot be over 350 ft³; vehicle class can't be blank"}

No

If retries don't resolve it, either request a different vehicle type for the order or use another provider that can supply the required vehicle in that area.

Requirements unsupported

"Age verification is not supported for this delivery" / "Signature on delivery is not available" / "Requested capability is not supported by this provider"

"errorCode": "unsupported_package_requirements", "errorMessage": "Provider does not support the following package requirements", with errorDetails.unsupported_requirements

No

Remove the unsupported requirement from the order, or choose a provider that does support it.

Address quality

"Unable to geocode the provided address" / "Address could not be verified" / "Apartment or suite number is required" / "PO boxes are not supported"

unable to parse required attributes ['number', 'formatted_street', 'city', 'zip']

No

Clean up the address: add any missing apartment/suite number, remove PO boxes, and check for typos, then resubmit.

Contact data

"Recipient phone number is required" / "Invalid phone number format" / "This field is required."

{"error": {"code": "INVALID_PHONE_NUMBER", "message": "Provided US phone-number '+1111111' is invalid"}, "response_status": "400 BAD_REQUEST"}

automationFailure: "Missing dropoff phone number, error_code=INVALID_PHONE_NUMBER"

No

Look for the named field in the error and correct or fill it in (commonly the recipient's phone number or address field), then resubmit.

Provider account / config

Nash-authored (stable): "<provider> is not present in allowed_providers." Provider-side: "Store not found" / "Invalid external_store_id" / "Unauthorized" / "Invalid credentials."

"<provider> is not present in allowed_providers" (Nash-authored, stable). Provider-side has no fixed code.

No

Check if the provider is in the selected Dispatch strategy. Contact Nash support if further assistance is required.

Provider API errors

"Request timed out" / "Internal server error" / "Too many requests" / "Provider returned an unexpected response"

None specific — generic Nash wrapper around a 5xx, timeout, or 429.

Yes

Retry the quote. If it keeps failing after a few attempts, treat it as a provider outage and reach out to Nash support.