[meliaj]

Summary

The retry advice for destination_route_unavailable said to assign an available proxy to the route or remove the route. A browser's network.proxy_routes are set when the browser is created. The update endpoint only accepts network.allowed_hosts, so neither change is possible on a running browser. The row now says to create a new browser whose route uses an available proxy, or one without the route.

It also adds what to do when the route's proxy still exists, since deletion isn't the only cause: contact support with the error code.

Testing

• mint broken-links: no broken links found

---

Note

Low Risk
Documentation-only change to error recovery text; no runtime or API behavior changes.

Overview
Updates the Retry column for destination_route_unavailable in the proxy errors docs so recovery steps match how browsers work today.

Instead of telling users to assign a proxy to the route or remove the route (which isn’t possible on a running browser because network.proxy_routes are fixed at creation and updates only cover network.allowed_hosts), the doc now says to create a new browser with a route that points at an available proxy, or a new browser without that route.

It also adds guidance when the route’s proxy still exists: contact support with the error code, since deletion isn’t the only reason the route can be unavailable.

^{Reviewed by Cursor Bugbot for commit d3804c2. Bugbot is set up for automated code reviews on this repo. Configure here.}

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated
Kernel	🟢 Ready	View Preview	Oct 23, 2026, 10:40 PM

💡 Tip: Enable Automations to automatically generate PRs for you.

[meliaj]

Picked robertjamesprior to review: touched the changed code in proxies; nothing pending

[robertjamesprior]

verified the claim against the api: BrowserNetworkUpdate only accepts allowed_hosts ("Other network settings can only be set at creation"), and proxy_routes exists only on the create-time BrowserNetworkConfig -- so the old advice (reassign or remove the route) was indeed impossible on a running browser. also confirmed the proxy-still-exists case is real: the egress proxy fails a matched route whenever the upstream can't be resolved (provider binding / credential resolution), not just on deletion, so the contact-support sentence covers a genuine cause.

one non-blocking wording nit: "or one without the route" can be read as "a proxy without the route" -- "or a new browser without the route" would be unambiguous.