> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/aperio-integration/configuring-the-aperio-locks-readers/configuring-status-report-and-polling-intervals.md).

# Configuring Status Report and Polling Intervals

### Status Report Interval

The status report interval is used by the communication hub to detect if the lock has gone offline. Any changes to this interval must be done on both the lock and communication hubs.

* If one lock is paired with the communication hub this is done automatically.
* If more than one lock is paired with the communication hub (AH30), the status report interval must be set through the communication hub right-click menu with a value, equal or higher than the longest status report interval for the locks paired.

### Polling Interval (V3 locks only)

Polling interval decides how often the lock wakes up and connects to the communication hub to check for information from the controller. Unlike a status report, where the lock status information is also sent to the controller.

Polling also allows the Aperio programming application to connect to the lock without the need of activating the radio with a credential (if set to less than 15 seconds). The default polling interval in the lock is 10 seconds.

### Procedure

1. In the Aperio Programming Application, **right-click** on the lock/reader and select **Lock/Sensor** > **Configure…**

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-9f894510c6d0b32618c3148f0afa8a8b1d870466%2Fconfigurestatus%26polling.png?alt=media)

   The Configure Lock/Sensor wizard displays.
2. Click **Next** until you reach the **Device Settings** screen of the wizard.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-2d402939705e4824fcd666a61aff5354169037d5%2Fconfigurestatus%26polling_2.png?alt=media)
3. Configure as required.

   <table><thead><tr><th width="175">To configure...</th><th>then...</th></tr></thead><tbody><tr><td>Status Report Interval,</td><td><ol><li><p>Click <strong>Change…</strong> in the Status Report Interval section of the screen.</p><p>The Configure Status Report Interval dialog displays.</p><p><img src="https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-196e364b35afcf30905162e25981ab4436230e21%2Fconfigurestatusreport.png?alt=media" alt=""></p></li><li><p>Enter the required status report interval.</p><p>(Default value of = 60 minutes)</p><p><strong>Note:</strong> Lowering the status interval time has an adverse effect on the battery life of the product.</p></li><li><p>Click <strong>OK</strong>.</p><p>The Configure Status Report Interval dialog closes.</p></li></ol></td></tr><tr><td>Polling Interval,</td><td><ol><li><p>Click <strong>Change…</strong> in the Polling Interval section of the screen.</p><p>The Configure Polling Interval dialog displays.</p><p><img src="https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f11a29ca69ea3e3ffd10d53564525f7da40ea26e%2Fconfigurepollinginterval.png?alt=media" alt=""></p></li><li>Ensure that the <strong>Disable polling</strong> checkbox is unticked and leave the polling time configured at its default value of 10 seconds.</li><li><p>Click <strong>OK</strong>.</p><p>The Configure Polling Interval dialog closes.</p></li></ol></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/aperio-integration/configuring-the-aperio-locks-readers/configuring-status-report-and-polling-intervals.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
