> For the complete documentation index, see [llms.txt](https://cbwire.ortusbooks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cbwire.ortusbooks.com/v2-1/template-features/polling.md).

# Polling

Poll for state changes based on a specified interval without page refreshes. Hot dog!

You can add a `wire:poll` directive to your elements to poll for changes using a set interval. The default interval is set to poll every *2 seconds*.

```xml
<div wire:poll></div>
```

You can append a different interval time to your directive as well.

```xml
<div wire:poll.5s> <!-- poll every 5 seconds --> </div>
```

{% hint style="success" %}
Polling for changes over AJAX can be a resonable alternative to strategies such as Pusher or WebSockets.&#x20;
{% endhint %}

## Method Invocation

If you would like to invoke a method during each poll interval, you can do so by specifying a method name.

```xml
<div wire:poll="refreshTasks"></div>
```

```javascript
component extends="cbwire.models.Component" {
    
    function refreshTasks() {}
}
```

## Cancel Polling

If you want stop polling, you can simply no longer render the HTML element that has the `wire:poll` directive.

```html
<cfif args.shouldPoll>
    <div wire:poll="refreshTasks"></div>
<cfelse>
    <div><!-- No more polling --></div>
</cfif>
```


---

# 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://cbwire.ortusbooks.com/v2-1/template-features/polling.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.
