Has there been a removal of round robin toggle within a provider?

[AlbertNg02]

To be clear, in 9router, there is an option so that if I had 4 antigravity accounts, there is an option to have the calls to them be round robin. As Omniroute was improved upon 9router, I found it a bit strange that that options is not present in omniroute. Currently there can onyl be a priority set.

The round robin in the combo is for different models while the round robin I am talking about is within 1 provier with multiple account so the accounts usage has a good spread.

The author mentioned this which I think is great:
#340 (comment)
but should there be both options ?
We could avoid this by adding a backoffLevel (penalizing failing accounts so healthy ones are prioritized) and a time decay (slowly lowering that backoff level over time so the penalized account isn't permanently starved of traffic and gets a chance to prove it's healthy again)."

[minhdangnguyenn]

Hi @AlbertNg02 ! Based on my research of the codebase and discussions:

Yes, the per-provider round robin toggle was not carried over
from 9router to Omniroute.

Currently Omniroute only supports priority-based selection
within a provider. The round robin across providers (different
models) exists, but not across multiple accounts of the same provider.

Workaround for now:
You can simulate load spreading by setting equal priority weights
across your accounts, though this won't give true round robin behavior.

Regarding the backoff approach mentioned in #340:
The backoffLevel + time decay suggestion is a solid alternative
that would achieve similar load distribution goals while also
handling failing accounts gracefully — arguably better than
strict round robin.

This seems like a worthwhile feature request if it doesn't exist yet!

[diegosouzapw]

Hey @AlbertNg02 (and thanks @minhdangnguyenn for the community answer)! Good news! While the old 9router concept was slightly altered, we have actually just brought back a form of true round-robin rotation for API keys inside a single provider connection in the v3.5.x series!

If you create a standard API Key connection, click "Advanced Settings". You will see an "Extra API Keys" section specifically built to handle round-robin rotation on every request through that single provider config!

We are also still planning to implement the backoff/decay mechanism for failing connections on the priority queue track. Let us know how the Extra API Key rotation works for you!