Skip to main content

Worker pools automatically de-prioritize drift detection jobs

Feature RequestsWorkersDrift Detection

<Stacks / Worker pools / Drift Detection> can now be configured to automatically de-prioritize drift detection jobs when worker pools are at capacity.

This feature allows non-drift detection jobs to automatically kill a running drift detection job to take its place. Killed drift detection jobs are re-queued <immediately / after a random delay / when at least one worker in the pool is idle for N minutes >

Status: ❌ Rejected1 comment

Log in to comment and vote

Comments1

  • Black Breeze

    •

    May 10, 2025

    Thanks for the suggestion! Drift detection jobs are already deprioritized behind user-initiated runs internally, so there’s no risk of them consuming worker capacity when more urgent tasks are waiting. If you’re seeing unexpected behavior, we’d love to dig into it—just reach out via support.