> 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/notifications-and-error-report.md). # Notifications and Error Report ### Run Completion We will inform you whenever a job is finished. This email contains information about the success of the last job(s), the duration, the amount of jobs and the cost. You can choose one of the following 4 options: * Never (you won't get any reports on your jobs). * With every run (you will receive a report after every finished job). * Daily (you will receive a daily report on your jobs). * Weekly (you will receive a weekly report on your jobs) To opt-out of run completion emails, choose the "Never" option. ### Error Report Independently of the job status, you can download an error report whenever there are failed responses in a job. To do that, go to the project details page and click on the number of responses in the row of the failed job or on the error report icon. The error report will open as a pop up and can also be downloaded as a JSON file.

--- # 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/notifications-and-error-report.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.