diegosouzapw/OmniRoute · error
${primaryConfig.id} failed (${result.status}), trying ${alte
Error message
${primaryConfig.id} failed (${result.status}), trying ${alternateConfig.id} What it means
Error "${primaryConfig.id} failed (${result.status}), trying ${alternateConfig.id}" thrown in diegosouzapw/OmniRoute.
Source
Thrown at open-sse/handlers/search.ts:1500
requestParams,
credentials,
startTime,
log,
connectionId,
apiKeyId
);
if (result.success) return result;
// 5. Failover to alternate (only for retriable errors and auto-select mode)
if (
alternateConfig &&
alternateCredentials &&
!NON_RETRIABLE.has(result.status || 0) &&
Date.now() - startTime < GLOBAL_TIMEOUT_MS
) {
if (log) {
log.warn(
"SEARCH",
`${primaryConfig.id} failed (${result.status}), trying ${alternateConfig.id}`
);
}
// Resolve alternate connection proxy independently so primary context never leaks
const fallbackResult = await tryProvider(
alternateConfig,
requestParams,
alternateCredentials,
startTime,
log,
alternateCredentials?.connectionId,
apiKeyId
);
if (fallbackResult.success) return fallbackResult;
}View on GitHub (pinned to a179ffed5b)
When it happens
Trigger: Thrown at open-sse/handlers/search.ts:1500 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of diegosouzapw/OmniRoute@a179ffed5b (2026-08-25).
Data as JSON: /api/errors/7b8d3ff440dcdf13.
Report an issue: GitHub.