Why Is UniFi Protect Not Retaining Detections As Expected?
- Policy mismatch by camera
- Storage pressure cleanup
- Version behavior change
Problem Description
When your UniFi Protect UniFi Detection Retention isn't working as expected, it usually traces back to one of a small number of causes — this guide covers them in order, starting with the most likely.
Symptoms
- Short detection history
- Missing past events
- Retention inconsistent
Recognize these? Here's what usually causes it.
Common Causes
- Policy mismatch by camera
- Storage pressure cleanup
- Version behavior change
Most fixes happen in the first 3 steps.
Do not assume global retention settings override camera-specific policies.
Tools & Requirements
Step-by-Step Solution
Review effective policies
Confirm retention values per camera and event type.
Check storage headroom
Low free space can shorten retained history.
Run validation window
Track known test event longevity against policy expectations.
Quick Solutions
Still having issues? This is usually the deeper cause below.
If the sensor still misses events after repositioning, check whether a scheduled 'home' or 'away' mode is overriding the sensitivity setting silently.
Retention expectations should be validated per camera role and risk level.
This issue almost always looks more complex than it is — the majority of cases trace back to a single setting, a stale credential, or a default that shipped wrong.
- Policy mismatch by camera
- Storage pressure cleanup
- Version behavior change
Before you go — try one of these (they fix most cases).
Need More Help? UniFi Protect Support
Note: The contact information below connects you directly to UniFi Protect's official customer support team, not Trunetto. They can help with warranty claims, device replacements, and advanced technical issues.