> 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/countdowns/manage.md).

# Manage countdowns

Find, filter, sort, edit, activate, duplicate, and delete the countdowns you've created.

The **Countdowns** page lists every countdown you've made, of every type. It's where you come back to check what's running, turn something on or off, or clean up.

## What the table shows

| Column         | Meaning                                                                      |
| -------------- | ---------------------------------------------------------------------------- |
| **Id**         | The countdown's internal identifier — the number you'll see in its shortcode |
| **Name**       | The name you gave it. Only you see this                                      |
| **Status**     | **Active** (live) or **Draft** (saved but not rendered)                      |
| **Type**       | Countdown timer, Estimated delivery date, Stock countdown, or Cart countdown |
| **Created at** | When it was created                                                          |

Click a row to open that countdown in the builder.

## Filter by status

Three tabs sit above the table: **All**, **Active**, and **Draft**. They're the quickest way to answer "what's actually live right now".

## Search

The search field looks across all your countdowns by name. It's the fastest way to find one when the list has grown past a screenful.

## Sort

The sort control offers:

* **Date** — **Newest first** or **Oldest first**
* **Countdown name** — alphabetically, ascending or descending

## Activate and deactivate

Status is what decides whether a countdown reaches your storefront. A **Draft** keeps its full configuration but is never rendered; flip it to **Active** and it starts appearing immediately, subject to its timing and conditions.

To change several at once, tick their checkboxes and choose **Set as active** or **Set as draft**. The app asks you to confirm before applying it.

{% hint style="info" %}
Deactivating a countdown is the safe way to pause a campaign. You keep every setting, and turning it back on is one click — no rebuilding.
{% endhint %}

## Duplicate

Select one or more countdowns and choose **Duplicate selected countdown(s)**. Each copy carries the same content, timing, conditions, and design.

This is the quickest route to a variation: duplicate a working timer, open the copy, and change just the end date or the collection it targets.

## Delete

Select the countdowns you want gone and choose **Delete selected countdown(s)**. The app asks you to confirm, and warns that the action can't be undone.

{% hint style="warning" %}
Deleting is permanent. A deleted countdown disappears from your storefront immediately and can't be recovered — if you might want it back, set it to Draft instead.
{% endhint %}

## Quick edits from the list

Timer countdowns can have their schedule adjusted without opening the full builder. The list's edit view exposes the **Time type** and the fields that go with it — **Start date** and **End date** for a date countdown, **Minutes** for a fixed-minutes timer — so extending a sale by a day doesn't mean a trip through the builder.

Anything else — text, design, conditions, position — is edited in the builder.

## Hitting a plan limit

If your store has reached the number of countdowns your plan allows, the page shows an error banner saying so when you try to create another. Delete or reuse an existing countdown, or move to a plan that allows more.

## Next steps

* [Choose a template](/samita-countdown-timer-bar/countdowns/templates.md)
* [Countdown types](/samita-countdown-timer-bar/countdowns/overview.md)
* [Display conditions](/samita-countdown-timer-bar/where-countdowns-appear/conditions.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/countdowns/manage.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.