Skip to main content

Relative priority of drift detection

Feature RequestsDrift Detection

Not all stacks drift detection runs are equally important. When the queue takes a bit longer to process, and drift detection runs are added to the queue, they are all done in chronological order, while (some) of the newer ones might be needing more priority.

When combined with “x time after last tracked run” this is still needed.

Status: ❌ Rejected2 comments

Log in to comment and vote

Comments2

  • Black Breeze

    •

    May 10, 2025

    Thanks for the feedback! Just to clarify—Spacelift treats all drift detection runs equally. If many are kicking off at the same time, they’ll compete for the same worker pool.

    A few things you can adjust:

    • Reduce frequency: Not every stack needs hourly checks.

    • Stagger schedules: Spread drift detection across the day with cron syntax.

    • Add workers: More concurrency = more throughput.

    There’s no prioritization setting today, and we’re not planning to add one. Best bet is to balance the load across time.

  • Natalia Gazda

    Team•

    Sep 16, 2024

    @Matt Anderson so currently drift detection runs, have lower priority over regular runs (so, in theory, it should work as you describe). It’s a default behavior, and we don’t provide any option to change that.

    Would you need anything more specific when it comes to the priority or scheduling of DD runs?