Skip to content

KV Limits page missing Delete and List operation limits #30857

@shai

Description

@shai

Existing documentation URL(s)

What changes are you suggesting?

What changes are you suggesting?
The limits table lists "Reads" and "Writes to different keys" but the Workers KV dashboard in the Cloudflare account UI shows four distinct operation types with separate counters: Read operations, Write operations, Delete operations, and List operations.

The limits table does not document whether Delete and List operations have their own daily limits on the free tier, whether they share the "Writes" quota, or whether they are unlimited.

This is a real operational gap: the account-level alert emails reference "KVoperations" generically when a threshold is hit, and without knowing which operation types count against which limits, it is impossible to diagnose what triggered the alert or what to fix.

Suggested additions to the limits table:

  • Clarify whether Delete operations have a separate daily free tier limit
  • Clarify whether List operations have a separate daily free tier limit
  • If Deletes and Lists share the "Writes" 1,000/day quota, state that explicitly
  • If they each have independent limits, add rows for them

The dashboard clearly tracks all four operation types separately, so the limits page should document them separately too.

Additionally, the upgrade pricing description in the alert email itself provides a useful clue: it states the paid plan "includes 10 million read operations and 1 million write, delete, and list operations", grouping write, delete, and list together as a single pool. If this same pooling applies to the free tier, the limits table should state it explicitly:

"1,000 write, delete, and list operations per day (combined)"

rather than the current "1,000 writes per day" which implies writes only.

Additional information

Image --- Image

Metadata

Metadata

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions