# Scheduling a pipeline and/or a release run
Imagine you want to trigger a release or a pipeline in frequent intervals say every hour, every day at a particular hour, or at a particular day in a week, Instead of going and doing it manually, users can create a Schedule for the particular use case they want according to their requirements for a release or a pipeline.
### **Steps to create a schedule for a release**
**Pre-requisites:**
* An Active cluster
* A Release created from Release Templates
**Steps:**
1. Once you log in to Ozone, select **Triggers** on the left-side bar.\
2.
```
```
3. After clicking on triggers a modal appears to select between **Schedules** and **Webhooks**\
Click on **Schedules** to get the schedules page
4.
```
```
5. After this users can click on the **Create Schedule** button to open the modal window for schedule creation
6.
```
```
7. This will open the modal window for **schedule creation**
8.
```
```
9. Users are provided options to select the frequency,\
**Hourly -** The release/pipeline will be triggered every hour, you need to enter the **minutes** on when to trigger the release/pipeline\
**Daily -** Release/Pipeline will be triggered daily, you just need to enter the **hours** and **minutes** when they want to trigger the Release and Pipeline\
**Weekly -** You can select the day of the week and the time on that particular day when they want to trigger the Release or Pipeline. You need to select the **day** and enter the **hours** and **minutes**\
Open image-20240416-090835.png
10.
```
```
11. Once the frequency is selected you can select the Resource type as Release\
Open image-20240416-091042.png
12. After selecting the Resource type as Release, an option will be provided to **select the release template** to choose the release template as desired. After all the details are entered and the release is selected, users can click on **map parameters** to move to the second step of schedule creation\
Open image-20240416-091435.png
13. Once all the details are entered, users can click on **Save** to create the schedule.\
Open image-20240416-091532.png
14. Once the Schedule has been successfully created it will be shown in the form of a tabular list, in the below way. In the table list view, you can see that the **next run** is visible and when next will the release will be triggered.\
Open image-20240416-091616.png
\
Users can click on the **edit button**, to edit the schedules\
Users can click on the **toggle button,** to enable/disable schedules\
Users can click on the **delete button**, to delete the schedules.
### **Steps to create a schedule for a pipeline**
**Pre-requisites:**
* An Active cluster
* Microservice
* Select the same environment in which the cluster has been created
**Steps:**
1. Follow the same steps as **schedule creation for release**, i.e. from step 1 - to step 6
2. Once this is done, select the resource type as **pipeline**\
Open image-20240416-091715.png
3. Now select the details for the following-\
\- Select the pipeline name, i.e. the pipeline that needs to be triggered\
\- Next, select the environment, the environment should be the same in which the cluster has been created\
\- Select the microservice\
\- Select the cluster\
Once all these details are entered click on the **map parameters** to move to the next step\
Open image-20240416-091808.png
4. The next step is to map parameters for the particular pipeline and enter the details as requested in the input run parameters. Once all the details have been entered, click on Save to create the schedule.\
\
The schedule created will be shown in the table list view as it was shown above while creating a release schedule.\
Open image-20240416-091842.png
\
---
# Agent Instructions: 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:
```
GET https://docs.ozone.one/ozone-end-user-guide/documentation/ci-cd/triggers/scheduling-a-pipeline-and-or-a-release-run.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.