> For the complete documentation index, see [llms.txt](https://docs.samita.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.samita.io/samita-countdown-timer-bar/countdown-timer/daily-recurring.md).
# Daily recurring timer
Run a timer on chosen weekdays between a start and end time, repeating every week.
A **Daily recurring timer** runs inside a window you define — for example every weekday from 9 am to 11 am — and counts down to the end of that window. Outside the window it shows nothing at all, and it comes back on its own the next time the window opens.
The app describes it as "Daily recurring timer." with the example "E.g. every weekday from 9 am to 11 am."
Use it for a happy hour, a lunchtime flash sale, a weekend-only promotion, or a daily deal.
## Steps to set it up
{% stepper %}
{% step %}
### Create the countdown
Click **Create countdown** from the dashboard or the **Countdowns** page.
{% endstep %}
{% step %}
### Pick a Countdown timer template
Leave the type tab on **Countdown timer**, choose a design, and click **Select**.
{% endstep %}
{% step %}
### Name it
Something that captures the schedule, like "Weekday happy hour 9–11".
{% endstep %}
{% step %}
### Write the text
On the **Settings** tab, open **Content** and set the **Title**, **Subtitle**, and timer labels. Copy that suits a repeating window — "Today's deal ends in:" — reads better than a one-off deadline. See [Timer text and button](/samita-countdown-timer-bar/countdown-timer/content.md).
{% endstep %}
{% step %}
### Choose Daily recurring timer
In **Setting timer**, set **Time type** to **Daily recurring timer.**
The section changes to show three groups of fields: a date range, the weekdays, and the daily time window.
A recurring timer needs a date range, the weekdays, and the daily hours.
{% endstep %}
{% step %}
### Set the campaign's date range
Under **Date between**, set **Start date** and **End date**. This is the outer boundary — the whole recurring campaign only runs between these two dates.
Set the End date far in the future for an open-ended promotion, or to the end of the month for a month-long one.
{% endstep %}
{% step %}
### Pick the weekdays
Under **Weekday**, tick the days the timer should run: Monday through Sunday. All seven are selected by default — untick the ones you don't want.
Tick only the days the offer runs.
{% endstep %}
{% step %}
### Set the daily window
Under **Time between**, set **Start time** and **End time**, each with hours, minutes, and seconds.
On every selected weekday, the timer appears at the Start time and counts down to the End time. The defaults are 9:15 to 10:15.
{% endstep %}
{% step %}
### Choose what happens at zero
Set **When countdown timer end**. **Hide countdown block** is the natural fit — the window closes, the timer goes, and it returns tomorrow. See [When the timer ends](/samita-countdown-timer-bar/countdown-timer/when-the-timer-ends.md).
{% endstep %}
{% step %}
### Style it, place it, and save
Adjust the **Design** tab if you want, then on the **Display** tab tick **Product page** or copy the **Shortcode**, and narrow it with **Conditions** if needed.
Set the status to **Active** and click **Save**.
{% endstep %}
{% step %}
### Check it during the window
Open a matching page on your live storefront while the window is open — the timer should be visible, counting down to the End time.
Check it outside the window too. Seeing nothing then is the correct result, not a fault.
{% endstep %}
{% endstepper %}
## How the window is evaluated
Three things must all be true for the timer to show:
1. Today falls inside the **Date between** range.
2. Today is one of the ticked **Weekday** days.
3. The current time is between **Start time** and **End time**.
If any one fails, nothing renders.
The check runs against the shopper's own device clock and calendar. A shopper several timezones away therefore sees the window at *their* 9 am, not yours — which is usually what you want for a "happy hour", but is worth knowing if your promotion is tied to a specific moment in your own timezone. For that, use [Count down to a date](/samita-countdown-timer-bar/countdown-timer/count-down-to-a-date.md) instead.
{% hint style="info" %}
Nothing appearing when you expect it to? Check the End date hasn't already passed, and that today is one of the ticked weekdays. Both are easy to leave behind after a campaign has run for a while.
{% endhint %}
## Next steps
* [When the timer ends](/samita-countdown-timer-bar/countdown-timer/when-the-timer-ends.md)
* [Count down to a date](/samita-countdown-timer-bar/countdown-timer/count-down-to-a-date.md)
* [Countdown not showing](/samita-countdown-timer-bar/help/countdown-not-showing.md)
* [Display conditions](/samita-countdown-timer-bar/where-countdowns-appear/conditions.md)
---
# 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://docs.samita.io/samita-countdown-timer-bar/countdown-timer/daily-recurring.md?ask=&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.
