Repository navigation
Conversation
Reclassify failures as transient (one-time or intermittent), permanent, or negative results: - Error handling best practices: fold intermittent into transient, add a Negative results section, and note that a permanent Activity failure doesn't have to fail the Workflow - Retry Policies, Python error handling, Application failures: same reclassification; business rule violations are negative results that code can choose to model as failures - Tasks: note that the declined-card example is a choice, not the only option - Detecting Workflow failures: replace an incorrect example of a Workflow Task that checks a remote data source
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
📖 Docs PR preview links
|
This branch was successfully deployed
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.
Summary
Aligns the failure-handling guidance with the Durable Execution categories: transient failures (one-time or intermittent), permanent failures, and negative results.
Stacked on the PR that adds
/durable-execution. Retarget tomainafter it merges.Changes
Code samples that model outcomes such as
InsufficientFundsas non-retryable failures are unchanged. That remains a valid choice for handling negative results.Verification
yarn buildandyarn check-linkswere run on the combined stack.vale --config .vale-ci.iniis clean on all touched files.