> 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/running-a-manual-job.md).
# Running a manual job
In addition to scheduled runs, you can trigger a job manually using one of the following options:
1. While setting up a project, you are prompted to choose the scraping frequency. Find the "Just scrape once" option from the dropdown menu. Choosing this option and clicking on "save project" ensures the job will be triggered right away and will run **only once**.
2. You can manually start a job, by clicking on the "Run job now" button inside the project details page. This option is available for all projects, so it does not matter if the status is "Scheduled" or "Not scheduled".
{% hint style="danger" %}
A new job can only be started if there are no other running jobs. All jobs have to be finished (project-specific), in order to start a new one.
{% endhint %}
---
# 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/running-a-manual-job.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.
