fix(routes): keep the 12 s budget from arrival and name the outage to voice

Starting the upstream timeout after the outbound queue let a request run
up to about 19 s, past the Directions layer's 15 s; the budget again runs
from arrival, queue wait included, and a budget spent before the request
leaves the queue answers 429 "routing busy" rather than an outage.

plan_route threw "Routing HTTP 502" for an outage, and voice passes only
the message on; it now throws "Routing service unavailable (HTTP 502)".

Co-Authored-By: Claude Opus 5.5 <[email protected]>
This commit is contained in:
quanticsoul4772andClaude Opus 5.5 committed 2026-11-02 09:21:08 -08:00
1 parent 536f371dde
commit 1bff1961b4
6 files changed
+53 -25

No files matched your search

+4 -4
View File
@@ -1,4 +1,4 @@
- A routing service outage (an error status, no answer or a non-JSON body)
is reported as "routing service unavailable" instead of "no route found",
so voice route planning and the Directions layer no longer blame the
request (quanticsoul4772, #1509).
- When the routing service is down (an error status, no answer or a non-JSON
body), voice route planning hears "Routing service unavailable" and the
Directions layer shows "Routing unavailable" instead of "no route found",
so neither blames the request (quanticsoul4772, #1509).