[24.2] Serialize message exceptions on execution error #19483
Merged
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 fixes handling of
ToolInputsNotOK
exceptions, which would fail withThis also required making the tool form error modal dependent on the returned errors, instead of only popping up on non-200 status codes or if all jobs failed.
That's what submitting the
Tag elements
tool that requires datasets in OK state looks like if one dataset is in failed_metadata state.This is much better than the just showing the API request as we used to do, and all the info is there for the UI team to show exactly which dataset is at fault.
Fixes #19482
How to test the changes?
(Select all options that apply)
License