Skip to main content

No Notifications Despite Drift

Problem
Status: 🗑️ Archived2 comments

Log in to comment and vote

Comments2

  • Apricot Cheetah

    •

    Sep 7

    Thanks for reporting this. To clarify the expected behaviour: when drift detection runs and detects drift, the drifted resources are flagged in the stack's Resources view, and the run itself appears under Account → Runs filtered to drift detection.

    A Slack notification can then be triggered through a notification policy that matches drift-detection runs — for example by checking run.drift_detection == true and routing the event to Slack.

    Notification policies are configured at the space level, so they apply to accessible stacks unless narrowed by stack name/labels — the policy needs to live in a space that covers the stack rather than being attached to it.

    If Slack notifications are not firing, please double-check that the policy conditions match drift-detection runs with actual changes, and that the stack runs on a private worker pool — drift detection requires one.

    If you're still having trouble, please reach out to support@spacelift.io and we'll be happy to help investigate.

    Here are some articles that you may find helpful:

  • Jonah Kowall

    Team•

    Sep 5

    If this is occurring it’s a bug, please contact support. I will point them here too.