Repository navigation
fix: log node and workflow failures - #139
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.
Failed nodes and unsuccessful workflows currently persist their errors without emitting an operator log record. Committed transitions to a failed node now emit one warning with workflow and node identifiers, node type, error kind and message, including tool-call visualization nodes inside successful agent runs. Committed unsuccessful workflow completions emit one error. Replaying an already-failed status emits no duplicate record; structured error details and payloads are excluded.
Validation: the native reporter proof fails before the fix and passes after it on SQLite and PostgreSQL. It executes a failing function and a failing agent tool, checks persisted outcomes, exact record counts, severity, identifiers, messages, handled failures, duplicate status replay, and exclusion of private error details. Full native suites and lint use runtime v0.3.59a with freshly resolved dependencies.
Compatibility: no registry, contract, configuration or stored data changes. The node operation result includes an optional failure projection for post-commit logging.