Skip to main content

Label skipped stacks on bulk operations as Skipped, not Failed

Feature Requests

Skipped stacks get grouped under the Failed stack even if it’s just something like an already Enabled stack getting skipped for a bulk Enable operation. It would be nice if these did not show as Failed.

Status: 🗑️ Archived3 comments

Log in to comment and vote

Comments3

  • Natalia Gazda

    Team•

    Jul 16

    Hey, thanks for the suggestion. We're archiving this one for now. It hasn't picked up much interest since it went up, so it isn't on our near-term roadmap. Archiving isn't deleting: the request stays on record, and if it gathers more votes or comments we can bring it back. If it still matters to you, add a vote or a comment so we can gauge the demand.

  • Black Breeze

    •

    Jun 9, 2025

    Hey Evan - we're digging into this and it raises a bigger question: should skipped operations change stack state at all? If a stack gets 'skipped' because it's already in the desired state (like already being enabled in a bulk enable operation), nothing actually happened to your infrastructure. So why should the stack's status change to reflect a non-event? What would you lose if skipped operations just left the stack state unchanged? The stack would keep its previous status instead of showing 'SKIPPED' - would that work better for you?

  • Amaranth Dew

    •

    May 29, 2025

    Skipped stacks get grouped under the Failed stack

    I typo’d here, I meant “Skipped stacks get grouped under the Failed status”