# Sensor Offline Cache

The Sensor Offline Cache stores device data with settings controlling when historical data is removed. New data is saved indefinitely unless it is updated by a newer record, whereby it is marked for deletion and appends a delete by date. This ensures that historical data about a device is available for an administrator to monitor, but is removed by a set date to free up space for newer records.

For example, a device returns that it has Windows 10 installed. This record will be stored in the database with a creation date and the deletion date set to `NULL`. A few months later, the device data is updated to Windows 11 and a new record is created. The existing Windows 10 record will now populate with a deletion date and will be purged from the database at set date/time while the Windows 11 record will remain.

{% hint style="info" %}
As of version 10.1.972.8, Sensor Offline Cache now defaults to 365 days for deletion and is enabled by default. If the setting was previous configured in a later version, this will NOT be overwritten.

In older versions, this data is saved indefinitely by default.
{% endhint %}

## Sensor Offline Cache Purger Settings

The time until deletion duration is determined by the Sensor Offline Cache Purger Settings.

![](/files/NbHhvCo6shFz5LHh3Zfk)

These settings can by found by navigating to **settings gear > Settings > Sensor Offline Cache**.

![](/files/2qGetnVNSvNRquCpGFgV)

Each of the following settings can be modified to suit your specific needs:

* **Purger Enabled** - When enabled (default), the purger clears sensor data at regular, user defined intervals.
* **Default Retention Period** - Determines how long stale sensor rows remain in the database before deletion.
* **Time Between Purge Starts** - Determines how often we kick off the process which deletes overly stale data.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.adaptiva.com/platform-guide/additional-settings/sensor-offline-cache.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.