Troubleshooting•stable•Updated 2026-07-06

Alert not triggered

Diagnose and fix alert not triggered.

Use this page when the symptom matches what you see in Kadryn or in your integration logs.

Symptoms

  • Expected alert did not appear.

Most common causes

  • Rule disabled.
  • No matching data.
  • Threshold not crossed.
  • Metadata or environment mismatch.

Fix

  1. Check alert rule state.
  2. Verify data in Costs.
  3. Check time range and filters.
  4. Review policy and signal inputs.

Verify the fix

  • Re-run the smallest safe test.
  • Open Logs & Traces and search by request ID, trace ID or resource ID.
  • Confirm the relevant dashboard card updates after refresh.
  • Confirm no retry loop or duplicate delivery was created.

When to escalate

Escalate when the issue affects production traffic, billing-sensitive reporting, audit evidence, or any workflow where a customer-facing AI feature is blocked.

Related pages