-
-
Notifications
You must be signed in to change notification settings - Fork 4.5k
feat(aci): redirect rules to automations with UI FF #103322
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
❌ 2 Tests Failed:
View the top 2 failed test(s) by shortest run time
To view more test analytics, go to the Test Analytics Dashboard |
| } | ||
| } | ||
|
|
||
| return children; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Bug: New UI Fails, Old Interface Returns
When the workflow-engine-ui feature flag is enabled and the API request completes without data (due to failure or missing workflow mapping), the component falls through to render the original alert rules UI. This creates inconsistent behavior where users with the feature flag enabled may still see the old UI when the API fails, rather than being handled explicitly with an error state or alternative redirect.
redirects issue alert specific routes to the appropriate automation pages