November 12, 2026. Cloudflare has announced a beta connector that lets AI Search index rows from its D1 database service. A supplied read-only query selects the source material; returned rows become searchable documents. This is a new ingestion option, not evidence that every answer is current or that every user should see every indexed record.
The operational question: what happens when content disappears?
Cloudflare's D1 documentation describes an important edge case: if a sync query fails or returns no rows, existing indexed items remain. Removing the final eligible source row is therefore not a reliable way to prove that its searchable copy has disappeared.
For a help center, that distinction could leave an obsolete answer available. For internal material, it makes access design a separate acceptance test. This is an operational implication of the documented behavior, not a claim of a demonstrated vulnerability.
A small pilot that can answer the right questions
- Start with approved material. Choose a small, non-sensitive collection whose intended readers are explicit. Do not treat the connector's read-only query as a substitute for authorization at the application boundary.
- Test removal as well as addition. Add a uniquely identifiable test article, change it, then remove it. Repeat with the last eligible row. Record the source state, sync result and actual search response rather than assuming that a successful database edit means the index changed.
- Define a withdrawal procedure. Decide how the application will stop serving content urgently if a sync has not completed. Check that procedure before importing anything that might need prompt removal.
- Budget for refreshes. D1 syncing reads the full query result at least twice. Shorter intervals therefore need a workload-based cost check, not an assumption that unchanged answers mean no database work.
Choose freshness deliberately
Cloudflare documents a 24-hour default sync interval, with configurable intervals down to 15 minutes. Treat those as scheduling choices, not a guarantee that a particular answer updates within that time. Monitor job history and test the end-to-end delay in your own pilot.
Scope: this report checks Cloudflare's announcement and documentation. We have not deployed or benchmarked the beta. The rollout is announced as available in beta, not generally available.
Primary sources: November 12 announcement; D1 data-source behavior; Sync scheduling and jobs.