Skip to main content

Show queued runs

Feature Requests

It’d be cool to see which stacks are queued for a run directly in the main Stacks view. Right now one can only see the status of the stack starting from “preparing”, and only inside a stack one could see there’s a “ready” run in the queue.

Problem
Status: ⬆️ Gathering votes3 comments

Log in to comment and vote

Comments3

  • Sapphire Honey

    •

    Jul 13

    I have a policy that requires approving runs on a specific stack. Before applying this policy, I used to trigger plans and even approve them from my saved views(in the sacks list) and could follow the progress of my runs across all involved stacks from there.

    After applying the policy, I now have to go stack by stack to approve it, the views seem to not show me that a stack is pending my approval, nor let me approve it from there.

    It would be great to see in the stacks list when a stack is pending approval. Even better would be the ability to approve or deny an approval flow triggered by policy drectly from the stacks list, the same way you can approve or deny a plan.

    As I cannot see that if stack is waiting for approval I sometimes trigger multiple times the same stack which have queues runs waiting for an approval(approve of the policy)

  • Green Goggles

    •

    Jun 30, 2025

    I second this request.

    One of the related issues I’m facing right now is that many stacks appear as “Finished” but if you go into the runs, there are newer runs queued. This happens because of dependencies that are unconfirmed, so the stack is waiting to be applied.

    Because of this, we get the unreal idea of all the stacks in the latest version, all applied and sync but it’s not true.

    There’s no visibility at all of all these stacks, nor in the filters, the views, or the workers. The only option is go one by one on all the stacks to check if the last run is applied or not.

    TL;DR; I’d add a new stated: “QUEUED”

  • Natalia Gazda

    Team•

    Jun 3, 2025

    Hey @Stefano Zanella, could you please tell me a bit more?

    • If you see which stacks have queued, would you follow up with any action? So, how would you use that knowledge?

    • How often does this happen?

    • Are you using any workaround currently?