Include exception properties in failure details when orchestration throws directly - #482
Merged
Merged
Conversation
Naiyuan Tian (nytian)
requested review from
andystaples,
Varshitha Bachu (bachuv) and
sophiatev
October 20, 2025 23:44
Contributor
Author
|
@microsoft-github-policy-service rerun |
andystaples
approved these changes
Oct 21, 2025
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
2 participants
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.
This PR fixes an edge case where, if an orchestration using DurableTaskWorker throws an exception directly, the exception properties were not included in the failure details even when a custom exception provider was configured. Also add two more comprehensive test cases for the exception properties provider.
Fix PR: Azure/durabletask#1251