{"version":"2.1.228","anchor":"gateway-answers-503-when-customer-routed-inference-keys-are-","canonical_anchor":"gateway-answers-503-when-customer-routed-inference-keys-are-","heading":"Gateway answers 503 when customer-routed inference keys are unavailable","tier":"soon","area":"Gateway","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228\/e\/gateway-answers-503-when-customer-routed-inference-keys-are-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228","markdown":"### Gateway answers 503 when customer-routed inference keys are unavailable\n\nIf key material can't be fetched, the gateway answers 503 with a retry hint instead of an auth error.\n\n**What**\n\nWith `cri.enabled` on, a bearer token routed through the customer-routed authenticator whose verification key material cannot be fetched now gets a 503 and a `Retry-After: 30` header, rather than being reported as an authentication failure.\n\n**Evidence**\n\n`customer-routed inference is temporarily unavailable: the gateway cannot obtain current verification keys`\n\n- Area: Gateway\n- Names: `cri.enabled`\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}