Why Is Frigate Event Retention Deleting Clips Too Early?
- Retention mismatch across sections
- Storage pressure purge
- Config override in include chain
Problem Description
When your Frigate Frigate Retention Policy 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
- Missing recent clips
- Retention shorter than configured
- Evidence window too small
Recognize these? Here's what usually causes it.
Common Causes
- Retention mismatch across sections
- Storage pressure purge
- Config override in include chain
Most fixes happen in the first 3 steps.
Do not rely on assumed defaults when using included config fragments.
Tools & Requirements
Step-by-Step Solution
Inspect effective config
Confirm final loaded retention values for events and recordings.
Check storage pressure
Low free space can force earlier cleanup behavior.
Retest lifecycle
Create test event and verify expected retention duration.
Quick Solutions
Still having issues? This is usually the deeper cause below.
If this comes back after following these steps, check whether a recent app or firmware update reset a default setting — the fix works, but the setting gets reverted silently.
Retention policy should be validated after every config refactor.
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.
- Retention mismatch across sections
- Storage pressure purge
- Config override in include chain
Before you go — try one of these (they fix most cases).
Need More Help? Frigate Support
Note: The contact information below connects you directly to Frigate's official customer support team, not Trunetto. They can help with warranty claims, device replacements, and advanced technical issues.