> For the complete documentation index, see [llms.txt](https://docs.avoautomation.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avoautomation.com/avo-assure/create-and-execute-tests-with-design-studio/optimizer-beta/features-in-optimizer/scheduling-a-prompt.md).

# Scheduling a Prompt

The Schedule selected allows you to schedule the selected prompts to run at a specified time or frequency. The prompts run automatically according to the selected time and date.

To run the selected prompts at a scheduled time, perform the following actions:

1. On the **Home** page, under **Projects**, select the required project.
2. Select **Design Studio** > **Optimizer**.
3. Select the required prompt and select **Schedule selected.** The **Schedule** dialog opens.
4. Select an option from the **Repeat** dropdown: 

* **Manual Run**: Runs the prompt only when you select **Run**.
* **Daily**: Runs the prompt every day at the selected time.
* **Weekly**: Runs the prompt every selected week on the selected day and time.

5. Select **Schedule**. The selected prompts run at the scheduled time and generate the results.

{% hint style="info" %}
**Note**: Select **Cancel** to close the dialog.
{% endhint %}


---

# 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.avoautomation.com/avo-assure/create-and-execute-tests-with-design-studio/optimizer-beta/features-in-optimizer/scheduling-a-prompt.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.