> 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/help/countdown-not-showing.md).

# Countdown not showing

A short checklist for when a countdown you've saved isn't appearing on your storefront.

Almost every "it's not showing" case comes down to one of five things: the embed, the status, the conditions, the timing, or the placement. Work down the list in order — the first two catch most of them.

## Find your symptom

| What you're seeing                     | Usually means                                           | Go to     |
| -------------------------------------- | ------------------------------------------------------- | --------- |
| Nothing from the app appears anywhere  | The app embed is off for this theme                     | Step 1    |
| One countdown is missing, others work  | It's a Draft, or its conditions don't match             | Steps 2–3 |
| It worked yesterday, not today         | Its end date passed, or you're outside its daily window | Step 4    |
| It shows on some products, not others  | Conditions, or a stock threshold                        | Steps 3–4 |
| It works on desktop but not mobile     | Device targeting                                        | Step 5    |
| It's missing on one page only          | Nothing has placed it there                             | Step 5    |
| A collection condition matches nothing | The collection template file is missing                 | Step 6    |

## The checklist

{% stepper %}
{% step %}

### Is the app embed on for *this* theme?

This is the most common cause by a wide margin, and it hides everything at once.

The embed is per theme. Enable it on your live theme, preview a different one, and nothing renders there.

Open the app's dashboard and check the app embed card, or open [Theme integration](https://github.com/samita-baoan/doc-timer/tree/restructure/docs-v2/settings/theme-integration.md) and select the theme you're actually looking at. If it says Inactive, turn it on — see [Turn on the app embed](/samita-countdown-timer-bar/quick-start/enable-app-embed.md).
{% endstep %}

{% step %}

### Is the countdown Active?

A **Draft** is saved but never rendered. Open the [Countdowns list](/samita-countdown-timer-bar/countdowns/manage.md) and check the Status column, or use the **Active** tab to see everything that's actually live.
{% endstep %}

{% step %}

### Do its conditions match the page you're on?

Open the countdown's **Display** tab and read the **Conditions** section against the page you're testing.

Two things catch people out:

* **All conditions vs Any condition.** Two collections joined with **All conditions** matches nothing, because no product is in both. Use **Any condition** to widen.
* **A Page condition combined with something else** needs **All conditions**, otherwise the page rule is satisfied on its own.

Customer conditions are worth checking in a private window — your admin session isn't a signed-in storefront customer.

See [Display conditions](/samita-countdown-timer-bar/where-countdowns-appear/conditions.md).
{% endstep %}

{% step %}

### Should it be visible right now?

Each type has its own reason to be legitimately invisible:

| Type                        | Check                                                                                                                                                                                                                                          |
| --------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Countdown timer**         | The **Start date** hasn't arrived, or the **End date** has passed and it's set to **Hide countdown block**. For a daily recurring timer: today isn't a ticked weekday, or you're outside the time window, or the outer **End date** has passed |
| **Estimated delivery date** | Nothing timing-related hides it — go back to conditions                                                                                                                                                                                        |
| **Stock countdown**         | The product's stock is **above** your "Only show if stock qty is equal or less than" threshold. Test on a genuinely low-stock product                                                                                                          |
| **Cart countdown**          | The cart is empty. It only appears when the cart has items                                                                                                                                                                                     |

Testing a **Fixed minutes** timer repeatedly in the same browser will keep showing you your own expired one — its state is kept in a cookie. Use a private window for each fresh test.
{% endstep %}

{% step %}

### Has it been given somewhere to render?

A countdown with the right conditions still needs a position.

* **On product pages**, tick **Product page** under **Show countdown on**.
* **Anywhere else**, the countdown needs a shortcode in a **Samita Countdown** app block on that page. A Page condition that allows a countdown on your collection pages doesn't place it there — see [Place a countdown with a shortcode](/samita-countdown-timer-bar/where-countdowns-appear/shortcode.md).
* **Check Device targeting** at the bottom of the Display tab. A countdown set to desktop only won't appear on a phone.

{% hint style="info" %}
Automatic product-page placement works by finding your theme's Add to cart area. On a heavily customised theme the app may not recognise it, and nothing renders. The fix is the shortcode: it puts the countdown exactly where you place the block, regardless of the theme.
{% endhint %}
{% endstep %}

{% step %}

### Only if you use a Collection condition

The **Collections** condition needs one extra template file in your theme. Without it, the app can't tell which collections a product belongs to on the storefront, and the condition matches nothing.

The app shows a warning banner in the builder when this file is missing. See [Enable the Collection condition](/samita-countdown-timer-bar/where-countdowns-appear/collection-search-file.md).
{% endstep %}
{% endstepper %}

## Still nothing?

A few less common causes:

**You're looking at a cached page.** Shopify and any CDN in front of it can serve a cached copy for a short while. Hard-refresh, or open the page in a private window.

**You're previewing a different theme.** Theme preview links are easy to leave open in a tab. Check the URL for a `preview_theme_id` parameter.

**A browser extension is blocking it.** Content blockers occasionally catch app scripts. Test with extensions disabled, or in a different browser.

**Two countdowns are competing.** If several match the same page, they all render. What looks like the wrong one showing is usually two active countdowns with overlapping conditions.

## What to send support

If you've worked through the list, [contact support](/samita-countdown-timer-bar/help/contact-support.md) with:

* Your store URL, and your storefront password if the store is password-protected.
* The name of the countdown that isn't showing.
* The exact page URL where you expect it.
* What you expected and what you actually see.
* A screenshot.

That set is usually enough to answer without a round of questions.

## Next steps

* [Turn on the app embed](/samita-countdown-timer-bar/quick-start/enable-app-embed.md)
* [Display conditions](/samita-countdown-timer-bar/where-countdowns-appear/conditions.md)
* [Place a countdown with a shortcode](/samita-countdown-timer-bar/where-countdowns-appear/shortcode.md)
* [FAQ](/samita-countdown-timer-bar/help/faq.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/help/countdown-not-showing.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.