Automatic Fault Code Deduplication

What is this?

Equipment sends the same fault code repeatedly. A DEF warning might fire every 10 minutes for hours. Without deduplication, your fault code dashboard fills up with hundreds of identical entries. Clue handles this automatically using a 30-day rolling window and configurable auto-dismiss rules.

How it works

When a fault code arrives from an OEM source (Samsara, John Deere, CAT, etc.):

• Clue records it in the fault code log (every occurrence is preserved for history)
• The system checks your auto-dismiss rules for a matching Code Identifier
• If a rule exists, all matching codes within the 30-day window are automatically dismissed
• Dismissed codes stay in the history log but do not appear in your active alerts

This is the same system as the Fault Code Rules Engine. When you set a rule to Auto-Dismiss, it handles deduplication for that code automatically.

The full details

• Time window: 30 days (rolling). Codes older than 30 days are outside the dedup scope.
• Every occurrence is recorded. Raw data is never lost. Dedup only affects the active alert view.
• Configured per code. Set auto-dismiss rules in Company Settings > Configuration > Fault Code Rules.
• Works across all OEM sources. Samsara, Tenna, John Deere, CAT. Same rules apply regardless of where the code came from.

Tips

• Start with your noisiest codes. Check which codes fire most often and set auto-dismiss rules for the ones that do not need attention.
• Use Log Silently instead of Auto-Dismiss if you want trend data. Both remove the code from active alerts, but Log Silently makes it easier to analyze patterns later.
• The 30-day window covers most cases. If a code fires repeatedly over weeks, all instances within the window get handled by one rule.