> For the complete documentation index, see [llms.txt](https://docs.abtasty.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.abtasty.com/flagship-deprecated/steps-configuration/using-the-scheduler.md).

# Using the scheduler

## 📖 Definition

The scheduler enables you to **automatically toggle a use case ON (launch) or OFF (pause) at a specific date and time** depending on your needs.\
Using the scheduler enables you to save time and to anticipate the activation or deactivation of a use case, particularly when you are located in a different timezone or outside of working hours.

## ⚙️ Configuration

You can schedule a use case to be launched and/or paused at a future date directly from the dashboard by hovering over the use case and clicking the schedule button.\
\
![Schedule-click.png](/files/RRrxf8psDQI8DHiGe4dp)

| <p>🚩 Heads up</p><p>Scheduling a Progressive Rollout will redirect you to the Deployment step. From there, you will be able to define the different deployment dates, including the starting and ending ones.</p> |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |

From the modal, you can choose to schedule your use case to be launched and/or paused at a specific date. To do so:

1. Activate the **Start** and/or **Stop date** toggle.
2. Select the date and time.\
   If you want to schedule only the start or stop date, only toggle ON the one you need.
3. Select the **timezone** from the drop-down list.
4. Click **SAVE.**\
   |

   🚩 Heads up

   You can launch and/or pause a scheduled use case at any time using the ON/OFF toggle from the dashboard. This action will unschedule your use case.

   \| | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

Once set up, the scheduled use case will be easily identified from the dashboard thanks to a schedule icon next to the status button.

![Scheduled.png](/files/T39Z37AaLNVxqF9DZo33)

| <p>⭐ Good to know</p><p>If you want to be notified when your scheduled use cases start or stop, you can use our <a href="https://flagship.zendesk.com/hc/en-us/articles/360021125079">Zapier integration</a> or our <a href="https://flagship.zendesk.com/hc/en-us/articles/360021123019">Webhooks</a>.</p> |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

## 💡 Use case

Let’s say you are working in California and have configured a use case that you want to launch for visitors located in Paris on the 24th of December at 10:00 PM, Paris time.\
To do so:

1. From the dashboard, click the schedule icon from your use case.
2. Toggle the **Start date** ON.
3. Select the date from the calendar: 24th of December 2021.
4. Select the time: 10:00 PM.
5. Select the **Europe/Paris** timezone.
6. Click SAVE:\
   Your use case will be activated at that date and no stop date is scheduled.

![schedule\_2.png](/files/RtIR5VDnlccQb9tMfVUK)

**Need additional information?**

Submit your request at <product.feedback@abtasty.com>

Always happy to help!


---

# 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.abtasty.com/flagship-deprecated/steps-configuration/using-the-scheduler.md?ask=<question>&goal=<endgoal>
```

`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.