fix(plugin-record-hook): rethrow errors instead of swallowing them #874
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.
Please explain how to summarize this PR for the Changelog:
fix(plugin-record-hook): Errors during record hook execution are now properly propagated instead of being silently swallowed. Previously, errors were logged but the function would return normally, causing executions to appear successful even when record updates failed.
Tell code reviewer how and what to test:
Context: This fix addresses an issue where bulk record hook updates could fail silently. When
event.update()failed, the error was caught, logged, and then the function returned without indicating failure. This caused agent executions to be marked as successful even when validation results weren't persisted.Changes:
returntothrow eso errors propagate to the listener runtimeReview checklist:
@flatfile/listener'sAuthenticatedClient.fetch()which swallows errors. This fix helps surface errors that DO get thrown, but won't catch cases wherefetch()silently returnsundefinedTo test:
event.update()(e.g., network error, invalid data)Requested by: christopher.harrison@flatfile.io (@cnharrison)