Problem: We regularly end up with hundreds of failed stacks due to unpinned dependencies and provider drift. Today, it’s extremely manual to determine which failures are identical vs. which are unique across environments, components, and regions.
Request:
Add failure grouping in the UI or via a downloadable report, ideally based on stack output. Group failures by exception type or error pattern so teams can quickly identify and resolve the root causes without clicking into every individual stack.
Impact: Helps large orgs triage & remediate faster, saves engineering time, and enables actual prioritization of real vs. noisy issues.
Please authenticate to join the conversation.
⬆️ Gathering votes
💡 Feature Requests
8 months ago
Get notified by email when there are changes.
⬆️ Gathering votes
💡 Feature Requests
8 months ago
Get notified by email when there are changes.