feat(ACI): Hide team metric alerts triggered component in workflow engine UI#114504
Merged
feat(ACI): Hide team metric alerts triggered component in workflow engine UI#114504
Conversation
github-actions
Bot
added
the
Scope: Frontend
saponifi3d
approved these changes
Apr 30, 2026
Contributor
saponifi3d
left a comment
saponifi3d
left a comment
There was a problem hiding this comment.
👍 for now, nothing is better than broken. we can also always revisit this and just update to use workflow fire history.
| 'Alerts triggered from the Alert Rules your team created.' | ||
| )} | ||
| > | ||
| <TeamAlertsTriggered |
Contributor
There was a problem hiding this comment.
🤔 should we just update the url to get the workflow fire histories?
not sure how many folks use this page / data. it doesn't seem like a lot since it's broken tho...
Member
Author
There was a problem hiding this comment.
yeah that was our thought (Nick and I), see if anyone even notices it's gone and if they do we can update
3 tasks
cleptric
pushed a commit
that referenced
this pull request
May 5, 2026
…gine UI (#114504) This component hasn't been able to load because it relies on incident data that we no longer write - however it's in a rather buried page and we haven't heard anything from customers about it not working. We're going to hide it behind the workflow engine ui flag (which is being GA'd next week) and see if anyone notices / cares. If they do, we can work on updating it with ACI data. **without (local)** <img width="1085" height="716" alt="Screenshot 2026-04-30 at 3 03 56 PM" src="https://github.com/user-attachments/assets/b38b7585-bb13-4f45-94f2-814db3fe0ede" /> **with (local, no alerts to be spoken of)** <img width="705" height="720" alt="Screenshot 2026-04-30 at 3 06 29 PM" src="https://github.com/user-attachments/assets/ad0ca1f9-e531-43f2-b3cc-b1773da8bbf7" /> **with (prod, there are alerts but it spins until it times out)** <img width="1379" height="273" alt="Screenshot 2026-04-30 at 3 09 59 PM" src="https://github.com/user-attachments/assets/e0eed8cd-7302-49e5-9d8e-c495041cefc2" />
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.
This component hasn't been able to load because it relies on incident data that we no longer write - however it's in a rather buried page and we haven't heard anything from customers about it not working. We're going to hide it behind the workflow engine ui flag (which is being GA'd next week) and see if anyone notices / cares. If they do, we can work on updating it with ACI data.
without (local)
with (local, no alerts to be spoken of)
with (prod, there are alerts but it spins until it times out)