# Data Feeds: Schedule & freshness

> Interval, staleness and the runtime tick.

Glider documentation · Data · Web page: https://cgglider.com/docs/pollers/schedule/

Sections of this page: [Transports](https://cgglider.com/docs/pollers.md) · [JSON, XML & text](https://cgglider.com/docs/pollers/formats.md) · [Webhooks](https://cgglider.com/docs/pollers/webhook.md) · [WebSockets](https://cgglider.com/docs/pollers/websocket.md) · [HTTP requests](https://cgglider.com/docs/pollers/compose.md) · [Auth & secrets](https://cgglider.com/docs/pollers/auth.md) · [Mapping the response](https://cgglider.com/docs/pollers/mapping.md) · [Schedule & freshness](https://cgglider.com/docs/pollers/schedule.md) · [Probe & diagnostics](https://cgglider.com/docs/pollers/probe.md)

| Field | Meaning |
| --- | --- |
| Interval ms | How often to poll. Default 1000. |
| Stale ms | If no payload lands within this window — a poll, a message or a push — mark the feed stale and degraded. |
| Fresh path | A boolean store path written true on a good payload and false on a failure, a dropped connection or staleness. |

The engine ticks every 100 ms, and the interval is quantised to that tick — an interval of 250 ms actually polls every 300 ms. A poll runs immediately when the unit starts rather than waiting out the first interval.

> **Bind the fresh path:** On air, a frozen number looks identical to a correct one. Bind the fresh path to something visible — a dimmed state, a hidden badge — so the gallery can see the feed has stopped answering.