> 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/working-with-execution-section/execute-execution-list/scheduler.md).

# Schedule

Users can schedule the test case executions multiple times at regular intervals**.** They can choose the start date, end date, repeat type using the schedule feature**.** Execution will start automatically at the scheduled time without any user intervention.

{% hint style="info" %}
**Note**: The **Scheduler** supports execution only through the **Agent** and does not allow execution through the **Client**. You must make sure the agent is installed, configured, and active before scheduling and triggering an execution. To learn how to **Install and Configure the Agent**, [click here](/avo-assure/administration/authentication-configuration/agent-management.md).
{% endhint %}

#### Features <a href="#features" id="features"></a>

1. **Start Date and Time:** User can mention the start and end time for the execution of the test case.
2. **Repeat:** Select if you want to repeat the job.
3. **Re-run this job**: Select how frequently you want the job to repeat. Example: Every Once/ Twice, In day, week, month.
4. **Ends:** Select a date when you want to end the job, Or You can select after how many occurrence you want to end the execution.
5. **Schedule:** Once all details are filled. Click Schedule button so that the profile scheduled successfully.

#### Steps to Create Schedule <a href="#steps-to-create-schedule" id="steps-to-create-schedule"></a>

1. Select **Start Date and Time**
2. Select **Repeat Checkbox.** This will enable the Re-run this job field. Select Recurrence.
3. Select End date for execution. You can also select after how many occurrences you want execution to stop.
4. Click **Schedule.** Your Execution list will be successfully scheduled.

<img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2Fq0M8ihMyJLptyhqoLAXV%2Funknown.png?alt=media&amp;token=99597a37-0012-4a15-ba6e-0c10c14a3cdc" alt="" height="281" width="605">


---

# 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/working-with-execution-section/execute-execution-list/scheduler.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.