fix: retry UNAVAILABLE errors from the Routes API - #312
Merged
Merged
Conversation
copybara-service
Bot
force-pushed
the
cl/981928761
branch
3 times, most recently
from
September 15, 2026 21:16
1c3097a to
8e807a8
Compare
Transient UNAVAILABLE responses from the Routes API are no longer cached, so a subsequent identical request can reach the service instead of replaying the cached failure. PiperOrigin-RevId: 982039246
copybara-service
Bot
force-pushed
the
cl/981928761
branch
from
September 15, 2026 21:22
8e807a8 to
7c8bc05
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
fix: retry UNAVAILABLE errors from the Routes API
Transient UNAVAILABLE responses from the Routes API are no longer cached, so a
subsequent identical request can reach the service instead of replaying the
cached failure.