You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit c4264fd
Browse filesBrowse the repository at this point in the historyBrowse files
fix(relay): tunnel recovery no longer drives the Cloudflare API into rate limits
Host recovery requests re-ran a full tunnel provision (list, ingress,
DNS, token) even when the tunnel was ready for the same origin, and the
Cloudflare SDK slept through every 429 until the relay's 8 s timeout.
On 2026-10-19 that tipped the account into sustained rate limiting:
links and recoveries both stalled into 503/504 and their retries kept
the limit in place.
- Recovery of a ready tunnel for an unchanged origin now only checks the
tunnel exists and fetches its token, falling back to a full provision
otherwise. Links still fully provision.
- Cloudflare rate limits are no longer retried inside the request, and a
429 pauses this isolate's Cloudflare calls for its Retry-After so
callers fail fast instead of extending the limit.
Refs #16810
Co-Authored-By: Claude Opus 5.5 <[email protected]>
0 commit comments