feat(sdk): surface operation error and attempt on OperationInfo#673
Merged
Conversation
The checkpointed Operation already carries per-operation Error (on Step/
Callback/Context/ChainedInvoke details) and Attempt (on StepDetails), but
toOperationInfo() only mapped Result, so onOperationChange consumers could
never see them.
- Add error?: Error and attempt?: number to the public (experimental)
OperationInfo type.
- Map them in toOperationInfo(): attempt from StepDetails.Attempt, error via
DurableOperationError.fromErrorObject() using the same *Details fan-out as
result. No new lifecycle hooks required.
- Workflow Insight plugin now serializes attempt and error { name, message }
into OperationRecord (stack trace and errorData intentionally omitted).
result remains available on OperationInfo but is not yet emitted in the record;
deferred to content filtering due to unbounded size.
yaythomas
approved these changes
Jul 1, 2026
ParidelPooya
marked this pull request as ready for review
July 1, 2026 06:21
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.
The checkpointed Operation already carries per-operation Error (on Step/ Callback/Context/ChainedInvoke details) and Attempt (on StepDetails), but toOperationInfo() only mapped Result, so onOperationChange consumers could never see them.
result remains available on OperationInfo but is not yet emitted in the record; deferred to content filtering due to unbounded size.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.