@Omer Norman We need more details regarding your setup.
I am going to assume you are using an Azure DevOps pipeline:
Make sure that the pipeline is not paused. If it is paused, it will not run even if it has a schedule set up. You can check this by going to the pipeline's settings and looking at the "Status" field.
- Check the pipeline's triggers to make sure that the schedule is set up correctly. You can do this by going to the pipeline's YAML file and looking for the "triggers" section. Make sure that the "schedule" trigger is set up correctly with the desired time and frequency.
- Check the pipeline's history to see if there are any errors or warnings related to the schedule trigger. You can do this by going to the pipeline's "Runs" tab and looking for any failed or partially succeeded runs.
- Check the pipeline's agent pool to make sure that it has the necessary resources to run the pipeline. If the agent pool does not have enough resources, the pipeline may not run even if it has a schedule set up.
If you are not using Azure DevOps Pipelines or we assumed wrongly, can you please provide more information about the type of pipeline you are using and the YAML file you have created? Also, have you checked if the pipelines are in a paused state? If the pipelines are paused, they will not run even if they have a schedule set up.