> For the complete documentation index, see [llms.txt](https://docs.scraperapi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.scraperapi.com/data-pipeline/creating-a-datapipeline-project/scraping-frequency.md).
# Scraping frequency
{% hint style="info" %}
The automatic scheduling is set to '**Just scrape once'** for every new project. You have to manually switch to another option while editing your project.
{% endhint %}
You can choose if you want to run a job manually or configure when your project should trigger jobs automatically. This is called "Scraping frequency". During project creation, you can find the dropdown for this option in the `Output settings` menu. Available options:
* **Don't scrape now**: No jobs will be triggered, only a project will be created. You can manually trigger a job from the project detail page. Read about this option [here](/data-pipeline/creating-a-datapipeline-project/running-a-manual-job.md).
* **Just scrape once (default):** A job will start once you click on "Save project".
* **Hourly, Daily, Weekly, Monthly:** The first job will start once you click on "Save project". The following jobs will be automatically fired based on the frequency you chose.
* **Cron:** You can set up your frequency by using the cron expression. You can learn more about cron-expressions [here](https://crontab.guru/).
You can also see when the next jobs are scheduled to run, based on the scraping frequency chosen in the settings.
### Disable job frequency
When you set the scraping frequency to "Don't scrape now", the project will be in a **"not scheduled"** state and jobs won't start automatically. You can manually start a job any time from inside the project's detail page. For more information, see [here](/data-pipeline/creating-a-datapipeline-project/running-a-manual-job.md).
---
# 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.scraperapi.com/data-pipeline/creating-a-datapipeline-project/scraping-frequency.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.
