unexpected status 503 Service Unavailable: Service temporarily unavailable: all targets were skipped by pre-dispatch filters

[shshicj-create]

I'm having this issue for the last 2 days and I couldn't solve it. can somebody help me to fix this problem?

[inbev92]

I had the same issue. In my case, the API key had access to the combo name, but not to all underlying models used by that combo. As a result, OmniRoute filtered out every target and returned all targets were skipped by pre-dispatch filters.

Check the API key’s model permissions and make sure it has access to:

• The combo itself
• Every provider/model configured as a target inside that combo

Alternatively, temporarily remove the model restrictions or set the key to full model access to confirm that permissions are the cause.

I resolved the problem by granting the API key full access to all models. After that, the combo started working normally.

[diegosouzapw]

Hey @shshicj-create! @inbev92 is right about one of the causes, and that 503 is deliberately diagnostic - the response body tells you exactly which targets were dropped and why.

ALL_TARGETS_SKIPPED means the combo resolved a non-empty target pool and then every single target was filtered out before any request was dispatched. Nothing was attempted, so there is no upstream error to report.

Read the diagnostics in the error body

The JSON body carries poolSize, attempted, excluded and terminalReason (open-sse/services/combo/roundRobinCombo.ts:1155). excluded is the list you want - it names each skipped target and the reason. Capture the full body, not just the message line:

curl -s -X POST http://localhost:20128/v1/chat/completions \
  -H "Authorization: Bearer $YOUR_KEY" -H "Content-Type: application/json" \
  -d '{"model":"YOUR_COMBO","messages":[{"role":"user","content":"hi"}]}' | jq .

The usual causes, in the order worth checking

1. API key scope (@inbev92's case): the key is allowed to call the combo but not every underlying model or connection. The expansion intersects with the key's allowedConnections, so a narrow key can empty the pool. Check Dashboard -> API Keys -> your key -> allowed models/connections.
2. Every connection is in cooldown: rateLimitedUntil in the future, or testStatus: unavailable. Dashboard -> Providers shows this per connection.
3. Provider circuit breaker OPEN: the whole provider is blocked after repeated 5xx. Check /api/monitoring/health.
4. Model lockout: per-model 429/404 on a specific connection, which skips just that model while the connection keeps serving others.
5. Quota window: when the skip was quota-driven, the message appends the quota detail in parentheses.

Paste the excluded array here and I can tell you which of the five it is.

[diegosouzapw]

@shshicj-create -- still happening on the latest version (3.8.52)? Otherwise I'll close this in 7 days for inactivity.