Skip to main content

Scheduled Reminders about unconfirmed Stacks

Feature RequestsUI/UXIntegrationsStacksNotifications

Similar to GitHub scheduled reminders, I would like to get reminded every day at a certain time about all my unconfirmed stacks, like “Hey, you have 13 unconfirmed stacks: (list of stacks).”

Ideally, I would be able to configure
- the channel this gets posted on
- a search query or space from which to list those stacks (generally, I care about stacks owned by my team, not the whole account)
- the schedule (maybe cron) this gets posted on
- types of stacks to include (unconfirmed, failed, drifted, etc.)

I would like to be able to configure an arbitrary number of such scheduled reminders (different sets of stack, different channels, different configs, etc.).

Maybe this should integrate with saved shared views of the stack list, and just let me do a scheduled reminder for an arbitrary shared view (which will post the reminder whenever there’s at least 1 stack visible in the view) - this would be very flexible then, easy to use, and integrate well with existing functionality.

Maybe this could similarly integrate with Notification policies. Instead of posting directly to slack, it would just trigger my notification policy with the list of stacks, and I would format the message myself.

Workaround
Problem
Status: ⬆️ Gathering votes2 comments

Log in to comment and vote

Comments2

  • Black Breeze

    •

    Dec 6, 2025

    I think we explored the idea in the past. What I was thinking was similar to AWS EventBridge rules where you’d specify a GraphQL query to execute on a schedule. The result along with the query metadata would then trigger a notification policy which could turn the data into a notification body.

    A few questions:
    - Where would you define these? On a space, presumably?
    - Who would these queries run as?
    - Does the level of effort involved in building this justify what sounds like an ultimate power user feature?

    Mind you that we’d be combining two things with a steep learning curve - Rego and GraphQL. I feel like we’d first need to lower the barrier for both, perhaps using AI, before offering a good experience on top of either, let alone on top of both.

    • Aquamarine Teacup

      •

      Dec 8, 2025

      I think “running arbitrary graphql queries” indeed sounds like quite a complex and involved feature primarily for power-users.

      But getting notified / reminded periodically about stacks you care about which need attention sounds like quite a basic feature with universal appeal to me.

      So I would like to avoid turning this feature request (which is arguably much more limited and oriented around a very specific common use-case) into something so extremely general (which also has multiple complex open questions to resolve, as you yourself say).