> 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/jobs-and-costs-management/job-status-and-cancellation.md).
# Job status & Cancellation
On the project overview page, you can see all project-relevant details and the status of your running and finished jobs.
### Jobs
When you start a job manually or automatically (based on the project's settings) it will appear in the first row of your jobs table. The job status indicates what stage the job is currently in:
* **Started:** Your job started and is in progress. You can see the progress and how many scrapes were finished and how many are still being processed.
* **Finalizing:** Before your job finishes (or returns an error), the status switches to finalizing. This means that all responses were processed and the final information and the results are being prepared.
* **Completed:** All responses were processed and your job has finished successfully. There might be responses with errors. You can learn more about the reasons behind the failed responses when you download the error report from column "No. of responses".
* **Error:** If more than 50% of your responses failed, we will show the status "Error". You can learn more about the reasons behind the failed responses when you download the error report from column "No. of responses".
* **Cancelling:** When you choose to cancel your running job, we stop sending new requests but it still waits for the running requests to finish. It might take a few minutes to finalize the job and to prepare the results.
* **Cancelled:** This is the status for cancelled jobs.
Clicking on "Progress details" inside the "Finished At" column triggers a pop-up window that displays the scraping progress in real time
---
# 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/jobs-and-costs-management/job-status-and-cancellation.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.
