> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/arm-1/arm-features/environment-provisioning/unsupported-metadata-templates/scheduleapexclassesweekly.md).
# Schedule Apex Classes Weekly
Using this template, the user can schedule an Apex class that implements the 'Schedulable' interface to be automatically executed on a weekly interval.
To create this template, follow the steps below:
1. Log in to your AutoRABIT account.
2. Click on **Env. Pro.** module.
3. Click on **Create New Template**.
4. Go to the **Create Unsupported Metadata Template** tab.
5. Give the template a **name** and a **short description** of it.
6. Select the **ScheduleApexClassesWeekly** checkbox available under **Schedule Weekly Apex Class Job**.
7. Click **Add**.
8. On the next screen, you'll notice that a **Test Case Name** appears by default. Click the **Add** button to add the custom test data. Fill in the required information in the fields below, then click the **Save** button.
* **Job Name** and **Apex Class:** give a name to the process in the **Job name** field; next, enter the **Apex Class**.
* Choose the preferred date and time for the process to be executed automatically.
9. Click **Save** to save the template.
10. Once the template is successfully created, you'll be redirected to the **Environment Provisioning History** screen.
11. Click the **Run** button to run the template on your destination org.
12. Select your **destination org** from the dropdown and enter the **email address(es)** to receive an email notification whenever the template is run.
13. In the **Post-Deployment Steps**, select the test cases that you have recently created.
14. Please check the **View History** page for a detailed summary report of the operation carried out.
---
# 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://knowledgebase.autorabit.com/product-guides/arm-1/arm-features/environment-provisioning/unsupported-metadata-templates/scheduleapexclassesweekly.md?ask=&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.
