Stop deleting Cloudflare R2 Iceberg files by hand

Cloudflare has added delete warnings for R2 buckets with Data Catalog enabled. Confidence level: confirmed. The change matters because Apache Iceberg tables rely on catalog transactions, so deleting objects directly from storage can leave table metadata pointing at missing files.

What changed

Cloudflare says the R2 dashboard and Wrangler now warn users before a manual delete operation runs on a bucket with R2 Data Catalog enabled. The warning is designed for a specific failure mode: changing objects outside the catalog can make an Apache Iceberg table inconsistent.

The dashboard warning lets users cancel or continue. Wrangler also checks whether the bucket has Data Catalog enabled before deletion and asks for confirmation. Cloudflare published the changelog entry on July 7, 2026, under R2.

Key takeaways

• The update targets manual object deletes on R2 Data Catalog-enabled buckets.
• The risk is table corruption, not ordinary file loss alone.
• Dashboard users see a warning with a link to the correct deletion guidance.
• Wrangler users get a confirmation prompt before continuing.
• Data teams should still delete rows, tables, snapshots, and orphan files through Iceberg-aware operations.

Availability and access

The warning is live in Cloudflare's R2 dashboard and Wrangler flow for buckets with R2 Data Catalog enabled. Cloudflare did not describe a paid-plan restriction in the changelog entry. The practical access check is simple: test a non-production bucket with Data Catalog enabled before changing cleanup automation.

This is not a replacement for Iceberg maintenance. Cloudflare's deletion guide still points users toward catalog-aware operations such as row deletes, dropping tables through an Iceberg engine, snapshot expiration, orphan-file removal, and compaction where appropriate.

Practical LinkLoot angle

This is a small platform change with a large operational lesson: object storage cleanup scripts should know whether a bucket is just object storage or an Iceberg-backed table store. If your team runs scheduled deletes, lifecycle jobs, or one-off cleanup commands against R2, add a Data Catalog check before the delete step.

For automation-heavy teams, treat this like a guardrail for agent and CI workflows too. A coding agent that sees "delete stale files" should not be allowed to clean a Data Catalog bucket with a generic object-delete command. Related workflow guidance lives in LinkLoot's AI workflow automation guide.

What to verify before you act

• Check whether the target R2 bucket has Data Catalog enabled.
• Confirm whether the data belongs to an Apache Iceberg table, not just raw object storage.
• Review cleanup scripts for direct object deletes, recursive removes, or broad prefixes.
• Use Cloudflare's R2 Data Catalog deletion guide for rows, tables, snapshots, and orphan files.
• Test Wrangler behavior in staging before running unattended production cleanup.

Source check

Confirmed by: Cloudflare's July 7 changelog entry for R2 Data Catalog delete warnings and Cloudflare's R2 Data Catalog deletion guide.

Context: Apache Iceberg's maintenance model explains why catalog-aware table maintenance matters. Iceberg tracks table state through metadata and snapshots, so storage-level deletes can break assumptions that query engines rely on.