diegosouzapw/OmniRoute · error
[STARTUP] Could not clear stale crash cooldowns (non-fatal):
Error message
[STARTUP] Could not clear stale crash cooldowns (non-fatal):
What it means
Error "[STARTUP] Could not clear stale crash cooldowns (non-fatal):" thrown in diegosouzapw/OmniRoute.
Source
Thrown at src/instrumentation-node.ts:312
]);
// Clear stale transient connection cooldowns persisted from an unclean crash.
// A crash mid-burst can leave far-future `rate_limited_until` values in the DB
// that cause every connection to be skipped by getProviderCredentials(), making
// all subsequent requests time out at Bottleneck's maxWaitMs (120 s default).
// Terminal states (banned / expired / credits_exhausted) are intentionally kept.
// See: https://github.com/diegosouzapw/OmniRoute/issues/3625 (Part A)
try {
const { clearStaleCrashCooldowns } = await import("@/lib/db/providers");
const { cleared } = clearStaleCrashCooldowns();
if (cleared > 0) {
console.log(
`[STARTUP] Cleared ${cleared} stale transient connection cooldown(s) from prior crash (#3625)`
);
}
} catch (err: unknown) {
const msg = err instanceof Error ? err.message : String(err);
console.warn("[STARTUP] Could not clear stale crash cooldowns (non-fatal):", msg);
}
await scanComboModelNameCollisionsAtBoot();
await warmAdaptiveVirtualLanesIntoRuntime();
const [
{ initGracefulShutdown },
{ initApiBridgeServer },
{ startBackgroundRefresh },
{ ensureCloudSyncInitialized },
{ startProviderLimitsSyncScheduler },
{ getSettings },
{ applyRuntimeSettings },
{ startRuntimeConfigHotReload },
{ startSpendBatchWriter },
{ startCleanupScheduler },
{ registerDefaultGuardrails },
{ ensurePersistentManagementPasswordHash },View on GitHub (pinned to a179ffed5b)
When it happens
Trigger: Thrown at src/instrumentation-node.ts:312 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/e35e9f098c1533db.
Report an issue: GitHub.