If key material can't be fetched, the gateway answers 503 with a retry hint instead of an auth error.
Only reachable with cri.enabled true, which defaults to false.
What's wrong with this entry?
With 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.
customer-routed inference is temporarily unavailable: the gateway cannot obtain current verification keys
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.221
Plugin install now tells you when higher-precedence settings keep it disabled
Both mention enabled
-
v2.1.223
Skills discovery skips disabled plugins
Both mention enabled
-
v2.1.227
claude gatewaynow identifies itself as the gateway providerBoth mention gateway