Troubleshooting Rules¶

Falkonry Rules let you define criteria on signals (raw or AI-generated) to trigger alerts and actions.

Problem	Solution
Evaluation Window, Density, and Coverage not set correctly	- Adjust parameters: - Evaluation Window – defines time range for criteria assessment. - Density – % of the window condition must hold. - Coverage – % of signals that must meet condition (multi-signal rules).
Categorical Signal Values mismatch	Ensure labels match exactly (case-sensitive).
Compound Rules not evaluating properly	Verify each contributing rule (AND/OR) evaluates to `True` as intended.
Alert Frequency settings block alerts	Check auto-snooze cadence: “Never”, “At most once per day/hour”, “Every time”.

Problem	Solution
Continuous or excessive alerts	- Adjust alert frequency (e.g., “At most once per day/hour”). - Increase evaluation window length. - Raise density %. - Raise coverage % (multi-signal rules). - Combine similar signals into one rule instead of many.

Problem	Solution
Need to rename rule already in use	- Not possible — rule names become output signal names and cannot be changed. Plan rule names carefully following naming conventions. - Create a new rule with desired name and delete previous rule and associated signals

Problem	Solution
Detecting degraded data quality or frequency issues	- Create rules that check for degraded quality or frequency changes. - Tip: Leaving the statistic dropdown empty counts data points, letting you trigger rules on unusual counts in a window.

Problem	Solution
Mixing signal types	- Rules must use all numeric or all categorical signals, never both.
Combining signals with very different ranges	- Avoid grouping signals with very different magnitudes or scales (e.g., current, speed, temperature) in the same rule.