fix(alerts): Surface API error messages in create/update toasts#115894
Merged
Conversation
…oasts Use getWorkflowEngineResponseErrorMessage to extract structured error messages from API responses when creating or updating automations, falling back to the generic message. This matches the pattern already used in the detectors hooks and the test notification mutation.
github-actions
Bot
added
the
Scope: Frontend
Contributor
📊 Type Coverage Diff✅ No new type safety issues introduced. Coverage: 93.56% |
JonasBa
pushed a commit
that referenced
this pull request
May 21, 2026
) The create and update automation mutation hooks were showing a generic "Unable to create alert" / "Unable to update alert" toast on any API failure, swallowing whatever message the backend actually returned. The detectors hooks already use `getWorkflowEngineResponseErrorMessage` to extract the first human-readable string from the error response JSON, so this applies the same pattern to `useCreateAutomation` and `useUpdateAutomation`.
3 tasks
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 create and update automation mutation hooks were showing a generic "Unable to create alert" / "Unable to update alert" toast on any API failure, swallowing whatever message the backend actually returned. The detectors hooks already use
getWorkflowEngineResponseErrorMessageto extract the first human-readable string from the error response JSON, so this applies the same pattern touseCreateAutomationanduseUpdateAutomation.