> For the complete documentation index, see [llms.txt](https://docs.hurrytimer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hurrytimer.com/troubleshooting/my-evergreen-timer-is-not-working-properly.md).
# My Evergreen timer is not working properly
If you have a caching plugin installed, you may encounter the following problems with your evergreen countdown timer:
* The countdown resets automatically each time you refresh the page
* The countdown has expired for all visitors
* The same countdown is showing up for all visitors
Since evergreen timers depend on cookies to recognize returning visitors, certain aggressive caching settings may result in this problem. To solve it, you need to exclude the timer cookie from caching. Please follow the instructions below to implement this setting in your caching plugin:
### Litespeed Cache
1. Go to Litespeed Cache menu > Cache > Excludes
2. Scroll down to **Do Not Cache Cookies**
3. Add your timers' cookies. For instance, if the timer ID is 1234, as shown in the screenshot below:
the cookie should be named `_ht_CDT-1234`, as demonstrated in the screenshot below.
### WP Rocket
1. Go to the WordPress settings menu > WP Rocket > Advanced Rules, and scroll down to **Never Cache Cookies**
2. Add the cookie `_ht_CDT`, as demonstrated in the screenshot below.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.hurrytimer.com/troubleshooting/my-evergreen-timer-is-not-working-properly.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.