im working on a monorepo with multiple workers, how do i get kv to work across workers with the same

Vvmg im working on a monorepo with multiple workers, how do i get kv to work across w...

H

Hello, I’m Allie!•7/10/25, 4:50 PM

Use the same directory via —persist-to

D

Dubz•7/10/25, 7:07 PM

Is there any native way to rename ~~containers~~ namespaces? I know it's referenced by ID and names whatever in workers, but for the sake of naming consistency it would be nice if I could change the name on the dashboard but not the ID.

DDubz Is there any native way to rename ~~containers~~ namespaces? I know it's referen...

H

Hello, I’m Allie!•7/11/25, 12:45 AM

Did you mean to ask in #containers-beta ?

HHello, I’m Allie!Did you mean to ask in #containers-beta ?

D

Dubz•7/11/25, 12:48 AM

my bad I meant namespaces

DDubz my bad I meant namespaces 😭

H

Hard@Work•7/11/25, 3:22 AM

Rename Namespace | Namespaces | KV | Cloudflare API

Cloudflare API | KV › Namespaces › Rename A Namespace

Interact with Cloudflare's products and services via the Cloudflare API

Kkoraytaylan i was trying to build a POC where i wanted to add items as a tree. keys would be...

T

thomasgauvin•7/11/25, 3:06 PM

thanks for the feedback, we're working on it in the dashboard & wrangler!

HHard@Work [Rename Namespace | Namespaces | KV | Cloudflare API](https://developers.cloudfl...

D

Dubz•7/12/25, 8:57 PM

Might need updated to use the newer API keys instead of global API key, but it does seem to have worked for me. Would be nice to have added to wrangler CLI tho to streamline

D

Dubz•7/12/25, 9:01 PM

Would be nice if namespaces could be sorted by name rather than ID. Make life a little easier

L

LukeZ•7/14/25, 6:04 PM

Guys, why the hell is metadata a required field? What should I pass there?
Because I know what "Body param: Arbitrary JSON to be associated with a key/value pair." means but I don't know why that is necessary...

L

LukeZ•7/14/25, 6:06 PM

LLukeZ Guys, why the hell is metadata a required field? What should I pass there? Becau...

I

Isaac McFadyen•7/14/25, 6:29 PM

If you don't have any metadata, set to the empty object

{}

{}

I

Isaac McFadyen•7/14/25, 6:29 PM

It's basically extra data to be attached to the KV entry that you can see in a

list

list

call if you need to

L

LukeZ•7/14/25, 6:29 PM

I have to send an empty string, but thanks!

IIsaac McFadyen It's basically extra data to be attached to the KV entry that you can see in a `...

L

LukeZ•7/14/25, 6:30 PM

aaah, interesting

LLukeZ Guys, why the hell is metadata a required field? What should I pass there? Becau...

T

thomasgauvin•7/15/25, 1:05 PM

It's needed in the REST API (can be empty object like Isaac mentioned) but is there a reason you are using the REST API instead of the binding?

L

LukeZ•7/15/25, 1:19 PM

because it's not a worker and I don't have my app deployed on workers because it is too much work for this simple, single use case

T

Tony Leung•7/22/25, 6:25 PM

hi guys, will Cloudflare eventually support bulk delete or bulk put in cloudflare KV using in Workers? CF workers has a limitation of 6 concurrent connection at the same time and it's really painful to bulk put like 20 - 30 items using the SDK in workers.

TTony Leung hi guys, will Cloudflare eventually support bulk delete or bulk put in cloudflar...

H

Hard@Work•7/22/25, 6:45 PM

Maybe put your question in #community-q-and-a ?

HHard@Work Maybe put your question in #community-q-and-a ?

T

Tony Leung•7/22/25, 6:45 PM

thanks, chaika has already answered it

sorry for posting it off-topic

H

Hth4nh•7/24/25, 7:05 PM

Hello everyone,

I'm encountering an issue with the Cloudflare Worker KV where I get an empty array when trying to retrieve multiple keys at once.

When I run the following code, it returns an empty array:

const values = await options.env.TEST.get(["2930", "2929"]);
console.log([...values.entries()]); // []

// Expected: [["2930", "foo"],["2929","bar"]]

const values = await options.env.TEST.get(["2930", "2929"]);
console.log([...values.entries()]); // []

// Expected: [["2930", "foo"],["2929","bar"]]

const values = await options.env.TEST.get(["2930", "2929"]);
console.log([...values.entries()]); // []

// Expected: [["2930", "foo"],["2929","bar"]]

const values = await options.env.TEST.get(["2930", "2929"]);
console.log([...values.entries()]); // []

// Expected: [["2930", "foo"],["2929","bar"]]

However, this alternative approach works as expected:

const values = await Promise.all(["2930", "2929"].map((key) => options.env.TEST.get(key)));
console.log(values); // ["foo", "bar"]

const values = await Promise.all(["2930", "2929"].map((key) => options.env.TEST.get(key)));
console.log(values); // ["foo", "bar"]

const values = await Promise.all(["2930", "2929"].map((key) => options.env.TEST.get(key)));
console.log(values); // ["foo", "bar"]

const values = await Promise.all(["2930", "2929"].map((key) => options.env.TEST.get(key)));
console.log(values); // ["foo", "bar"]

According to the documentation, passing an array of keys to the

get()

get()

method should return a

Map

Map

of the key-value pairs.

Here is my

wrangler.jsonc

wrangler.jsonc

file for reference:

{
    "$schema": "node_modules/wrangler/config-schema.json",
    "name": "***",
    "main": "./src/index.ts",
    "compatibility_date": "2025-06-20",
    "observability": {
        "enabled": true
    },
    "assets": {
        "directory": "./public/",
        "binding": "ASSETS"
    },
    "kv_namespaces": [
        {
            "binding": "TEST",
            "id": "***",
            "preview_id": "***"
        }
    ]
}

{
    "$schema": "node_modules/wrangler/config-schema.json",
    "name": "***",
    "main": "./src/index.ts",
    "compatibility_date": "2025-06-20",
    "observability": {
        "enabled": true
    },
    "assets": {
        "directory": "./public/",
        "binding": "ASSETS"
    },
    "kv_namespaces": [
        {
            "binding": "TEST",
            "id": "***",
            "preview_id": "***"
        }
    ]
}

{
    "$schema": "node_modules/wrangler/config-schema.json",
    "name": "***",
    "main": "./src/index.ts",
    "compatibility_date": "2025-06-20",
    "observability": {
        "enabled": true
    },
    "assets": {
        "directory": "./public/",
        "binding": "ASSETS"
    },
    "kv_namespaces": [
        {
            "binding": "TEST",
            "id": "***",
            "preview_id": "***"
        }
    ]
}

{
    "$schema": "node_modules/wrangler/config-schema.json",
    "name": "***",
    "main": "./src/index.ts",
    "compatibility_date": "2025-06-20",
    "observability": {
        "enabled": true
    },
    "assets": {
        "directory": "./public/",
        "binding": "ASSETS"
    },
    "kv_namespaces": [
        {
            "binding": "TEST",
            "id": "***",
            "preview_id": "***"
        }
    ]
}

I've also made sure that the

preview_id

preview_id

is correctly configured for use with

wrangler dev

wrangler dev

.

Has anyone else experienced this issue or has any idea what might be going wrong?

Thanks

M

mr.niko.la•8/1/25, 2:28 AM

Is kv able to temp hold 25mb file ?

For <60s

M

mr.niko.la•8/1/25, 2:28 AM

I need failover for r2 upload and prefer to use cf infra for latency before trying another s3

Mmr.niko.la Is kv able to temp hold 25mb file ? For <60s

I

Isaac McFadyen•8/1/25, 4:25 AM

25mb is the limit per KV value. It can hold any value up to 25mb indefinitely, yes.

P

Pingu•8/5/25, 5:07 PM

Do KV key expirations count as deletes for billing purposes?

C

cosbgn•8/7/25, 8:45 AM

Is KV down?

Ccosbgn Is KV down?

I

Isaac McFadyen•8/7/25, 1:38 PM

Are you still seeing these issues?

Original message was deleted

H

Hard@Work•8/7/25, 6:34 PM

?pings

S

SuperHelpflare•8/7/25, 6:34 PM

Please do not ping community members for non-moderation reasons. Doing so will not solve your issue faster and will make people less likely to want to help you.

IIsaac McFadyen Are you still seeing these issues?

C

cosbgn•8/7/25, 6:46 PM

Last was 21h ago

Y

yevgen•8/12/25, 9:25 AM

In case you missed it last week: https://blog.cloudflare.com/rearchitecting-workers-kv-for-redundancy/

The Cloudflare Blog

Redesigning Workers KV for increased availability and faster perfor...

Workers KV is Cloudflare's global key-value store, serving millions of requests per second across hundreds of billions of stored objects. The service powers critical infrastructure for dozens of Cloudflare products—from Access authentication to Pages static assets—making its availability essential to our platform's reliability.

After the in...

A

alison•8/18/25, 8:50 PM

There's a relatively well-documented issue with writing to KV where

metadata

metadata

is supposedly optional, but required in the type definition within the

cloudflare-typescript

cloudflare-typescript

library.

Easy, right? Just pass in a dummy empty

metadata

metadata

object on your writes to KV! WRONG!!

If you just do that, your value gets stored in KV as an object like

{ value: XYZ, metadata: {}}

{ value: XYZ, metadata: {}}

. Not super intuitive, I'd rather just store XYZ. So then I learned:

When passing in

metadata

metadata

, you actually need to include the

Content-Type: multipart/form-metadata

Content-Type: multipart/form-metadata

header (image 1, link). The library has some handling for automatically including this header, but it doesn't catch these cases where we're forced to pass in empty metadata

Logical next move is to just pass in the header. Ok cool, easy right? WRONG!

Now I get an error back:

{"code":10047,"message":"can not parse value and metadata from multipart request body: 'could not parse multipart request: 'no multipart boundary param in Content-Type''"}

{"code":10047,"message":"can not parse value and metadata from multipart request body: 'could not parse multipart request: 'no multipart boundary param in Content-Type''"}

{"code":10047,"message":"can not parse value and metadata from multipart request body: 'could not parse multipart request: 'no multipart boundary param in Content-Type''"}

{"code":10047,"message":"can not parse value and metadata from multipart request body: 'could not parse multipart request: 'no multipart boundary param in Content-Type''"}

Fair, but I feel I am entering hacky code land and am not exactly sure how to set and use a boundary param within the context of the API. Is it as easy as just passing something like

Content-Type: multipart/form-data; boundary=asfghjkl

Content-Type: multipart/form-data; boundary=asfghjkl

?

Has anyone run into this issue? If so, how did you fix it? Did you just take the L and take

.value

.value

on your GET response from KV, potentially running into issues when this finally gets fixed? Or did you manually pass in a fancy header? Or something else I am forgetting?

Here are some previous issues where people encountered the same thing: https://github.com/cloudflare/cloudflare-go/issues/3911, https://github.com/cloudflare/cloudflare-python/issues/2519

S

shinshin•8/25/25, 9:52 AM

When calling get using a key obtained from the list, null may be returned even if the key exists. Is this behavior caused by KV consistency?

const keys = await env.NAMESPACE.list();

Promise.all(keys.map(async (key) => {
  const v = env.NAMESPACE.get(key.name);
  console.log(v);
}))

const keys = await env.NAMESPACE.list();

Promise.all(keys.map(async (key) => {
  const v = env.NAMESPACE.get(key.name);
  console.log(v);
}))

const keys = await env.NAMESPACE.list();

Promise.all(keys.map(async (key) => {
  const v = env.NAMESPACE.get(key.name);
  console.log(v);
}))

const keys = await env.NAMESPACE.list();

Promise.all(keys.map(async (key) => {
  const v = env.NAMESPACE.get(key.name);
  console.log(v);
}))

Sshinshin When calling get using a key obtained from the list, null may be returned even i...

I

Isaac McFadyen•8/25/25, 3:43 PM

Depends, if the key was recently written then yes.

I

Isaac McFadyen•8/25/25, 3:43 PM

If the key has been present for a while you should see it fine though.

J

João Castro•8/25/25, 11:26 PM

I don't understand much about how KV is built, but would having something like https://blog.cloudflare.com/instant-purge/ possible or would it break the fundamentals of how it works? Sometimes the 60s delay for revalidating keys can be pretty annoying

The Cloudflare Blog

Instant Purge: invalidating cached content in under 150ms

Today we’re excited to share that we’ve built the fastest cache purge in the industry. We now offer a global purge latency for purge by tags, hostnames, and prefixes of less than 150ms on average (P50), representing a 90% improvement since May 2022.

IIsaac McFadyen 25mb is the limit per KV value. It can hold any value up to 25mb indefinitely, y...

M

mr.niko.la•8/27/25, 1:12 PM

Basically in a hyper rare case r2 upload fails due some reason can kv be used as failover ? Is that even worth doing or is cf automatically doing that? Or is it better to use something like backblaze ?

S

ShaneCodes•8/28/25, 1:27 PM

We use a ton of KV at Zephyr and I'm always poking around local KVs and was having a really hard time find the resources with the way they're stored. The SQLite table which has the actual keys mapped to the blob id. So I made a vscode plugin to connect the two and let me search them. I don't know if anyone else would find it useful but wanted to share

https://marketplace.visualstudio.com/items?itemName=swalkerdev.cloudflare-kv-explorer

Cloudflare KV Explorer - Visual Studio Marketplace

Extension for Visual Studio Code - Browse and inspect Cloudflare Workers KV stores during local development with Wrangler

S

ShaneCodes•8/28/25, 1:28 PM

I don't know if the dev tools are open source but I would really be down to add this functionality to the dev tools if I can

L

LukeZ•9/1/25, 5:17 AM

How much workload can a KV handle? How to make writes more efficient?

I'm planning on making a website where you can basically press just one button, but I want to keep track of how many times people pressed the button.

However, I know there are certain limits to the KV (reads & writes) so basically just getting the value and incrementing it would be too inefficient since it would be two requests to the KV every time the button is clicked.
So what would you guys suggest to make this more efficient?

LLukeZ ### How much workload can a KV handle? How to make writes more efficient? I'm p...

I

Isaac McFadyen•9/1/25, 5:18 AM

just getting the value and incrementing it would be too inefficient since it would be two requests to the KV every time the button is clicked.

Not only that, KV is eventually consistent. If you do a

get()

get()

in one datacenter and then increment and a

put()

put()

, another datacenter might not see it for up to 60 seconds so that datacenter might also do a

get()

get()

and a

put()

put()

(using the stale value) and then your counter is no longer consistent since a write would be lost.

I

Isaac McFadyen•9/1/25, 5:19 AM

I'd recommend another storage solution like Durable Objects or D1 for this use-case. KV is great for read-heavy workloads but not a good fit for workloads that need strong consistency like this.

IIsaac McFadyen > just getting the value and incrementing it would be too inefficient since it w...

L

LukeZ•9/1/25, 5:20 AM

Oh! Interesting to know

IIsaac McFadyen I'd recommend another storage solution like Durable Objects or D1 for this use-c...

L

LukeZ•9/1/25, 5:21 AM

Aight

I will take a look at this, thanks!

E

Eumatio•9/1/25, 2:54 PM

Hii! I wanted to know what is the reason for this limit, or if is just a bug?

const state = ulid(Date.now());

const stateData: StateData = {
    returnTo: safeReturn,
    codeVerifier: verifier,
    createdAt: Date.now(),
    expiresAt: Date.now() + this.STATE_TTL_MS
};

await this.stateDatabase.set(state, JSON.stringify(stateData), {
    expirationTtl: this.STATE_TTL_MS
});

const state = ulid(Date.now());

const stateData: StateData = {
    returnTo: safeReturn,
    codeVerifier: verifier,
    createdAt: Date.now(),
    expiresAt: Date.now() + this.STATE_TTL_MS
};

await this.stateDatabase.set(state, JSON.stringify(stateData), {
    expirationTtl: this.STATE_TTL_MS
});

const state = ulid(Date.now());

const stateData: StateData = {
    returnTo: safeReturn,
    codeVerifier: verifier,
    createdAt: Date.now(),
    expiresAt: Date.now() + this.STATE_TTL_MS
};

await this.stateDatabase.set(state, JSON.stringify(stateData), {
    expirationTtl: this.STATE_TTL_MS
});

const state = ulid(Date.now());

const stateData: StateData = {
    returnTo: safeReturn,
    codeVerifier: verifier,
    createdAt: Date.now(),
    expiresAt: Date.now() + this.STATE_TTL_MS
};

await this.stateDatabase.set(state, JSON.stringify(stateData), {
    expirationTtl: this.STATE_TTL_MS
});

W

Walshy•9/1/25, 5:13 PM

that looks like your STALE_TTL_MS is wrong

W

Walshy•9/1/25, 5:13 PM

it shouldn't be over/under 2 billion milliseconds

Aalison There's a relatively well-documented issue with writing to KV where `metadata` i...

T

thomasgauvin•9/3/25, 2:19 PM

Hey @alison & folks, we've recently released the v5.0.0 version of the

cloudflare

cloudflare

typescript SDK, which resolves the metadata bug reported above with workers kv updates and reads. You are now able to write, update & read the metadata from the typescript SDK! Go try it out

https://www.npmjs.com/package/cloudflare/v/5.0.0

npm

cloudflare

The official TypeScript library for the Cloudflare API. Latest version: 5.0.0, last published: 18 hours ago. Start using cloudflare in your project by running

npm i cloudflare

npm i cloudflare

. There are 124 other projects in the npm registry using cloudflare.

S

Sb•9/9/25, 1:48 PM

Hello,

Does reading and writing from the meta of the kv key-value count in the billing ?

SSb Hello, Does reading and writing from the meta of the kv key-value count in the ...

I

Isaac McFadyen•9/9/25, 1:49 PM

In order to access KV metadata you need to either make a

list()

list()

call (which is billed) or a

get()

get()

/

getWithMetadata()

getWithMetadata()

call (which is also billed). So yes.

S

Sb•9/9/25, 1:56 PM

Okay,

I want to make a counter which counts the no. of requests hitting my worker. Is there a better option for this value fetch ??

I was thinking of kv earlier but it is billable and expensive for a simple counter property as it requires write action in every request.

Is there a better way for this value to be accessible in the worker itself?

im working on a monorepo with multiple workers, how do i get kv to work across workers with the same

How much workload can a KV handle? How to make writes more efficient?

Similar Threads

Similar Threads

How much workload can a KV handle? How to make writes more efficient?

Similar Threads