Docs: short note about what happens when all providers are rate-limited

[awhite0030]

Quick thought while testing fallback today ✨

It might help if the README briefly mentioned the behavior when every configured provider hits rate limits (e.g. returns a clear error or queues?).

Just a one-liner so users know what to expect in the worst case.

Very low priority — capturing it while it’s fresh 😊

No rush.

[awhite0030]

Good point 👍

Yeah, when every provider is rate-limited the current behavior is just to surface a clear error so the client knows nothing is available right now. A short note in the README would make that expectation obvious for people self-hosting.

I’ll keep this in mind for the next docs cleanup.

[awhite0030]

Good point 👍

When all providers are rate-limited the current behavior is to surface a clear error to the client (no silent queueing yet). Might be worth spelling that out in the README so people know what to expect.

Leaving this open for now.

[awhite0030]

Good catch 👍

I’ve seen this edge case a couple times while testing heavy fallback scenarios. A short note in the README about the final error behavior would definitely help new users.

Maybe something like: “If every provider is rate-limited, the router returns a clear 429/503 with a short message instead of hanging.”

Happy to draft a one-liner PR later if nobody else grabs it first.

[awhite0030]

Makes sense 👍

When every provider is rate-limited the current behavior is a clean error response (no silent queue yet). A one-liner in the README would set the right expectation for users hitting the wall.

Leaving this as a low-priority docs note for now — might expand it later if we add any retry/queue logic.

[awhite0030]

Yeah, this would be useful.

Right now when everything is rate-limited the error can feel a bit opaque. A short note in the README (or even just a clearer error message) explaining that the router exhausted all fallbacks would save some head-scratching.

I’ll keep an eye on this when polishing the error handling. Thanks for writing it down 🙌

[awhite0030]

Still thinking about this one 🤔

A clear “all providers rate-limited” response (maybe with a short retry-after hint) would make debugging a lot easier when things get tight.

Keeping it as low-priority docs for now.

[awhite0030]

Makes sense. A clear "all providers temporarily unavailable" message (maybe with a short retry-after hint if any provider returns one) would be good enough for most cases.

Could also log it to the dashboard so you can see the spike later. Low priority though — the current error is already better than a silent hang 👍

[awhite0030]

Yeah, this is one of those edge cases that only shows up under real load. A short note in the README would be enough — something like “if all providers are rate-limited the router returns a clear error”. Keeps expectations realistic without over-documenting 👍