# DataPipeline Update: 10× Larger Jobs & 30-Day Data Retention Policy

## 1. 10x more URLs per job — up to 100,000

You can now submit up to **100,000 URLs, ASINs, or keywords** in a single DataPipeline project, up from the previous 10,000 limit. Larger jobs run in a single submission with no manual splitting required.

Just create a new project and start with a bigger list.

## **2. Result retention policy — 30 days**

DataPipeline job results will now be automatically deleted 30 days after job completion. This applies to all job output files and result payloads. Every job now includes a `results_expire_at`  field in the API response so you always know exactly when your results will be removed.

**Existing projects — grace period**

If you have existing DataPipeline projects created before this release, your results are safe until **2026-05-13**. Download any existing data before that date. After that, the standard 30-day policy applies to all jobs going forward.

**Why both changes together?**

The 100,000 URL limit significantly increases the result payload sizes we store per job. Introducing a clear retention policy at the same time keeps infrastructure costs sustainable as job volume scales — and gives you a predictable, well-communicated window to retrieve your data.

<a href="https://docs.scraperapi.com/data-pipeline/creating-a-datapipeline-project" class="button primary" data-icon="chart-diagram">VISIT DATAPIPELINE DOCS</a>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.scraperapi.com/resources/release-notes/april-2026/datapipeline-update-10-larger-jobs-and-30-day-data-retention-policy.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.