Cloudflare D1: review large results before November 4
A practical check for catalogues and reports before the new query-result limit: test coverage, record consistency and a reusable worksheet.
Cloudflare announced on October 30 that D1 query results will be capped at 50 MB from November 4, 2026. The enforcement date is still ahead.
Who should check
If your catalogue or internal report uses D1, give its developer a list of screens that load entire datasets. Using Cloudflare DNS alone does not imply using D1. This is not a new limit on AffiliateCore’s database.
Prepare the test
List each query, the screen calling it, the fields actually needed and response sizes at realistic data volumes. Test with an anonymised copy. A successful request against a tiny fixture does not prove readiness. The documentation exempts REST API import and export operations from this limit. An ordinary query feeding a custom CSV download does not become that export merely because of its filename.
Two learning scenarios
An affiliate catalogue. A page retrieves every description but displays only names. Compare displayed products and links before and after reducing the response; visit the first, an intermediate and the last page. Missing or repeated records mean stopping the release and fixing ordering. An internal report. A monthly download collects the entire history. Test bounded periods and reconcile unique records and final statuses against the original report. If records change during extraction, agree on a fixed snapshot; otherwise pages can disagree. These are hypothetical tests, not customer results.
Reusable worksheet
Copy and fill in: screen → owner → query → response size → unused fields → selection boundaries → stable ordering → unique-record check → test result → rollback method. Do not delete history to shrink a response. A row count alone does not guarantee a safe size. Our editorial acceptance criteria: pages open, records are complete and unique, and the original result is reproducible.
Next step
Use your AffiliateCore account to reconcile campaign results; diagnosing your D1 database remains your developer’s separate task. This check concerns projects using D1 regardless of site language. Confirm service access and regional conditions separately.