fix(aci): Gracefully handle missing actions in Alerts UI#112070
fix(aci): Gracefully handle missing actions in Alerts UI#112070
Conversation
…tions-in-alerts-ui
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 81a7f88. Configure here.
| > | ||
| {actionLabel ?? t('Unknown integration')} | ||
| </AutomationBuilderRow> | ||
| ); |
There was a problem hiding this comment.
API failure misreported as permanently unavailable actions
Medium Severity
When the useAvailableActionsQuery call fails (network error, 500, etc.), isLoadingActions becomes false and availableActions defaults to []. This causes getActionHandler to return undefined for every action, triggering the "no longer available" error message for all of them. Users could then be misled into deleting perfectly valid actions. The code checks isLoadingActions but not isError from the query, so a transient API failure is indistinguishable from a genuinely removed integration.
Reviewed by Cursor Bugbot for commit 81a7f88. Configure here.
When an action is no longer available, we were previously rendering `null`, which made it impossible to get the alert in a working state for saving. This PR renders an item which can be removed with a helpful message telling the user to add a new action.


Closes ISWF-2365
When an action is no longer available, we were previously rendering
null, which made it impossible to get the alert in a working state for saving. This PR renders an item which can be removed with a helpful message telling the user to add a new action.Before:
After: