Rule Not Triggering
Symptoms
- Rule is active but notifications never arrive
- Action history shows no executions
Diagnostic Checklist
Verify Rule is Active
Navigate to Automation > Rules and ensure:
- Rule status shows Active (green toggle)
- Rule is not in Test Mode (test mode only logs, doesn't execute)
Check Criteria Syntax
Open the rule and review the Criteria expression. Common mistakes:
| Mistake | Correction |
|---|---|
[Payload][Key = 'Temp'] AND [Payload][Value > 50] | [Payload][Key = 'Temp' AND NumericValue > 50] (same bracket) |
Key = Temperature | Key = 'Temperature' (quotes required) |
Value > 100 | NumericValue > 100 (use NumericValue for numeric comparisons) |
Verify Data is Flowing
Ensure the device generating data is active and connected. Check UNS Explorer for live values.
Check Rate Limiting
If rate limiting is enabled (e.g., max 10 actions per 60 seconds), additional triggers are ignored.
Expression Errors
"Invalid expression" when saving
The criteria parser couldn't understand the expression. Check:
- Balanced brackets: Every
[must have a matching] - Correct operators: Use
AND,OR,NOT(not&&,||) - String quotes: Use single quotes for strings:
'value'
"Column not found" error
You referenced a property that doesn't exist in the event type:
| Event Type | Available Properties |
|---|---|
| DataReceived | Payload, MetaData, Attributes, Topic |
| StatusChanged | DeviceId, DeviceName, CurrentConnectionStatus, PreviousConnectionStatus |
| LogReceived | Message, Level, Category, Source, Time |
| MetricsReceived | Device, TotalRequests, FailedRequests, AverageResponseTime, etc. |
See Expression Syntax Reference for complete list.
Actions Not Executing
Notification Not Sent
- Check Integration Configuration: Navigate to Integrations > Notifications and verify the channel (Email, Slack, etc.) is correctly configured
- Test the Integration: Use the Test button to send a test message
- Review Action History: Open the rule and check the History tab for error messages
Common Action Errors
| Error | Solution |
|---|---|
Channel not configured | Add the notification channel in Integrations settings |
Rate limited | Reduce rule trigger frequency or increase rate limit |
Authentication failed | Update API keys or tokens in integration config |
Anomaly Detection Not Working
Model Not Training
Anomaly detection requires historical data to build a baseline.
- Minimum Data: At least 100 data points for statistical significance
- Warm-up Period: Allow 1-2 hours of data collection before anomalies are detected
Too Many False Positives
Adjust the Sensitivity threshold:
- Lower value = fewer alerts (only extreme anomalies)
- Higher value = more alerts (minor deviations flagged)
lightbulb
Seasonal Patterns
If your data has daily/weekly patterns (e.g., higher values during work hours), the model will adapt over time. Allow 1-2 weeks for pattern learning.
See Also
- Expression Syntax Reference - Complete criteria language guide
- Visual Rule Editor - Build rules without code
- Actions & Alerts - Configure notification actions
- Notification Integrations - Email, Slack, Teams setup
- Data Flow Problems - If data is not reaching rules