Repository navigation
Show Python business-error retry classification and workflow handling - #370
Merged
Merged
Conversation
|
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
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 Python guide shows how to stop retries, but does not explain how wrapped errors are classified or how workflow code can handle a terminal business refusal. Add exact outer-exception name matching rules, a
NonRetryableError(..., cause=error)example, and a workflow that catches only the intendedActivityFailedand completes with a rejected result.Refs #343. All eight languages now contain matching examples and current source hashes. Published qualification verifies seven originals, including exact short/qualified matching, subclass/cause controls, and both inputs for the actual guide snippet. The SELECT-only audit proves attempt counts, continuation into another durable activity and zero repairs.
No SDK behavior or protocol change is claimed. Full exact-head documentation qualification 39925741408 passes the all-eight-locale build and strict links. CodeQL, Sonar (zero new issues/hotspots), protocol and boundary checks pass. Deployed-route verification follows publication.