Conversation
…cessing" as transient The Bedrock error message "The system encountered an unexpected error during processing. Try your request again." was falling through to ErrorClass::Fatal because the existing heuristic in classify_bedrock_error only matched the older wording "unexpected error when processing the request". When the error arrives without a usable service error code (e.g. a mid-stream event error), the message heuristics are the only signal, so the request was never retried. Add message heuristics for "unexpected error during processing" and "try your request again" to the Transient branch. Co-authored-by: Infinity 🤖 <infinity@hydro.run>
Deploying infinity with
|
| Latest commit: |
eb58ba3
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://3fd87843.infinity-dc7.pages.dev |
| Branch Preview URL: | https://sandbox-cfb54d5d-f060-4dd5-b.infinity-dc7.pages.dev |
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.
The Bedrock error message "The system encountered an unexpected error
during processing. Try your request again." was falling through to
ErrorClass::Fatal because the existing heuristic in
classify_bedrock_error only matched the older wording "unexpected error
when processing the request". When the error arrives without a usable
service error code (e.g. a mid-stream event error), the message
heuristics are the only signal, so the request was never retried.
Add message heuristics for "unexpected error during processing" and
"try your request again" to the Transient branch.