API-Created Proposed Runs Aren't Easily Viewable
Currently the only way to view runs triggered by the API (not via source control) is to view them in the global “Runs” view. There should be a section of the console for each stack similar to PRs/Tracked Runs that show these executions.
- Workaround
- the global runs view
- Problem
Log in to comment and vote
Comments2
Natalia Gazda
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
May 8, 2025
Thanks for raising this!
It sounds like you’re triggering proposed runs via the API but then needing to manually monitor them through the GUI. That suggests there’s some kind of automation or external system driving Spacelift, but it’s not currently pulling results or surfacing them in context—so you fall back to the global Runs view.
We’re curious: what are you building around these runs? Is this part of a broader control plane or automation workflow? Understanding the bigger picture could help us figure out whether better visibility should live in the GUI, or whether there’s a lighter way to expose that data where you already are.
Would love to learn more about the flow you’re trying to support—especially what you’d want to see per stack, and why.