TTL for unconfirmed jobs
It would be fantastic if we could TTL unconfirmed jobs into a discarded state. I dislike how a unconfirmed job will block a pipeline and future changes that come in. I understand why its done but if a change is sitting in our default branch I’d want to make sure its out there or reverted.
- Workaround
- Problem
Log in to comment and vote
Comments2
Purple Pumpkin
Sep 11, 2025
•Merged request
•1 vote
Make expiration time for unconfirmed tracked runs configurable
Currently, unconfirmed tracked runs in Spacelift automatically expire after a certain period. We’ve noticed this expiration is not configurable, and once a run expires it cannot be replayed. This can cause problems if a run is left unconfirmed for too long.
Black Breeze
May 10, 2025
Thanks for surfacing this! You’re absolutely right that stale unconfirmed jobs can pile up and create noise or even risk if acted on too late.
Today, Spacelift already supports this behavior—just through a different lens. You can use a push policy to automatically cancel outdated or in-progress runs. It gives you fine-grained control (by branch, commit age, etc.) and can replicate a TTL-like effect right now.
That said, we hear the underlying ask: “Can this be easier?” Some folks may not realize policies can solve this, or just want a dead-simple way to auto-expire old runs.
We’re exploring how to make this more discoverable and ergonomic—whether through a template in the Policy Library, or even a simple toggle that writes the policy for you. No promises yet, but we’re tracking this closely.
If you’re already hitting pain here, happy to help you implement a policy that fits your workflow—just reach out.