Hi, I’m getting a 429 error when writing to Workers KV via the HTTP API. The docs say the Enterprise

Mmackong Hi, I’m getting a 429 error when writing to Workers KV via the HTTP API. The doc...

T

thomasgauvin•12/15/25, 6:55 PM

Are you writing more than 1 time per second per key? That is a hard limit

Tthomasgauvin Are you writing more than 1 time per second per key? That is a hard limit

M

mackongOP•12/16/25, 2:55 AM

Thanks for the reply. The RESP API limits requests to 1,200 every five minutes.

Mmackong Hi, I’m getting a 429 error when writing to Workers KV via the HTTP API. The doc...

I

Isaac McFadyen•12/16/25, 2:57 AM

I believe you'll need to reach out to your CSM to get this limit relaxed, the part in the docs about it being unlimited on Enterprise is specifically regarding the Workers binding and the REST API is a seperate limit unrelated to KV.

IIsaac McFadyen I believe you'll need to reach out to your CSM to get this limit relaxed, the pa...

M

mackongOP•12/16/25, 3:28 AM

Yes, I’ve switched to using a worker to write to KV, but I see there’s no bulk write support. How can I write to KV concurrently from a worker? My code currently looks like

async function putKeys(env: Env, pairs: Array<Record<string, string>>): Promise<Response> {
  for (const pair of pairs) {
    var lastE = null;

    for (let i = 0; i < retries; i++) {
      try {
        await env.KV_NS.put(pair["key"], pair["value"], {
          metadata: {
            version: "v1",
            timestamp: ((Date.now() / 1000) | 0)
          }
        });
        console.log({"message": `Successful to sync key ${pair["key"]}`});
        break;
      } catch(e) {
        lastE = e;
      }
    }

    if (lastE != null) {
      console.error({"message": `Failed to sync key ${pair["key"]}`, error: lastE});
    }
  }
  console.log({"message": `Successful synced ${pairs.length} pairs`});

  return new Response(null, {});
}

async function putKeys(env: Env, pairs: Array<Record<string, string>>): Promise<Response> {
  for (const pair of pairs) {
    var lastE = null;

    for (let i = 0; i < retries; i++) {
      try {
        await env.KV_NS.put(pair["key"], pair["value"], {
          metadata: {
            version: "v1",
            timestamp: ((Date.now() / 1000) | 0)
          }
        });
        console.log({"message": `Successful to sync key ${pair["key"]}`});
        break;
      } catch(e) {
        lastE = e;
      }
    }

    if (lastE != null) {
      console.error({"message": `Failed to sync key ${pair["key"]}`, error: lastE});
    }
  }
  console.log({"message": `Successful synced ${pairs.length} pairs`});

  return new Response(null, {});
}

async function putKeys(env: Env, pairs: Array<Record<string, string>>): Promise<Response> {
  for (const pair of pairs) {
    var lastE = null;

    for (let i = 0; i < retries; i++) {
      try {
        await env.KV_NS.put(pair["key"], pair["value"], {
          metadata: {
            version: "v1",
            timestamp: ((Date.now() / 1000) | 0)
          }
        });
        console.log({"message": `Successful to sync key ${pair["key"]}`});
        break;
      } catch(e) {
        lastE = e;
      }
    }

    if (lastE != null) {
      console.error({"message": `Failed to sync key ${pair["key"]}`, error: lastE});
    }
  }
  console.log({"message": `Successful synced ${pairs.length} pairs`});

  return new Response(null, {});
}

async function putKeys(env: Env, pairs: Array<Record<string, string>>): Promise<Response> {
  for (const pair of pairs) {
    var lastE = null;

    for (let i = 0; i < retries; i++) {
      try {
        await env.KV_NS.put(pair["key"], pair["value"], {
          metadata: {
            version: "v1",
            timestamp: ((Date.now() / 1000) | 0)
          }
        });
        console.log({"message": `Successful to sync key ${pair["key"]}`});
        break;
      } catch(e) {
        lastE = e;
      }
    }

    if (lastE != null) {
      console.error({"message": `Failed to sync key ${pair["key"]}`, error: lastE});
    }
  }
  console.log({"message": `Successful synced ${pairs.length} pairs`});

  return new Response(null, {});
}

Mmackong Yes, I’ve switched to using a worker to write to KV, but I see there’s no bulk w...

I

Isaac McFadyen•12/16/25, 3:29 AM

You probably want to use standard Promise concurrency: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise/all

Note that Workers can only make 6 requests at once (that includes KV I believe) so you may need to use something like https://www.npmjs.com/package/p-limit

IIsaac McFadyen You probably want to use standard Promise concurrency: https://developer.mozilla...

M

mackongOP•12/16/25, 3:41 AM

Thank you very much

M

mackongOP•12/17/25, 3:52 AM

I’m getting a 403 when listing regional hostnames in a zone, even with DNS read/write permissions. Which additional permission is required?

M

mackongOP•12/17/25, 3:53 AM

The code is

const client = new Cloudflare({
  apiToken: CLOUDFLARE_API_TOKEN
});

console.log("List all Regional Services regions available for use by this account.");
for await (const regionListResponse of client.addressing.regionalHostnames.regions.list({
  account_id: ACCOUNT_ID,
})) {
  console.log(regionListResponse);
}

// Got `error: 403 {"result":null,"success":false,"errors":[{"code":1002,"message":"forbidden"}],"messages":[]}`
console.log("List all Regional Hostnames within a zone.");
for await (const regionalHostnameListResponse of client.addressing.regionalHostnames.list({
  zone_id: ZONE_ID
})) {
  console.log(regionalHostnameListResponse);
}

const client = new Cloudflare({
  apiToken: CLOUDFLARE_API_TOKEN
});

console.log("List all Regional Services regions available for use by this account.");
for await (const regionListResponse of client.addressing.regionalHostnames.regions.list({
  account_id: ACCOUNT_ID,
})) {
  console.log(regionListResponse);
}

// Got `error: 403 {"result":null,"success":false,"errors":[{"code":1002,"message":"forbidden"}],"messages":[]}`
console.log("List all Regional Hostnames within a zone.");
for await (const regionalHostnameListResponse of client.addressing.regionalHostnames.list({
  zone_id: ZONE_ID
})) {
  console.log(regionalHostnameListResponse);
}

const client = new Cloudflare({
  apiToken: CLOUDFLARE_API_TOKEN
});

console.log("List all Regional Services regions available for use by this account.");
for await (const regionListResponse of client.addressing.regionalHostnames.regions.list({
  account_id: ACCOUNT_ID,
})) {
  console.log(regionListResponse);
}

// Got `error: 403 {"result":null,"success":false,"errors":[{"code":1002,"message":"forbidden"}],"messages":[]}`
console.log("List all Regional Hostnames within a zone.");
for await (const regionalHostnameListResponse of client.addressing.regionalHostnames.list({
  zone_id: ZONE_ID
})) {
  console.log(regionalHostnameListResponse);
}

const client = new Cloudflare({
  apiToken: CLOUDFLARE_API_TOKEN
});

console.log("List all Regional Services regions available for use by this account.");
for await (const regionListResponse of client.addressing.regionalHostnames.regions.list({
  account_id: ACCOUNT_ID,
})) {
  console.log(regionListResponse);
}

// Got `error: 403 {"result":null,"success":false,"errors":[{"code":1002,"message":"forbidden"}],"messages":[]}`
console.log("List all Regional Hostnames within a zone.");
for await (const regionalHostnameListResponse of client.addressing.regionalHostnames.list({
  zone_id: ZONE_ID
})) {
  console.log(regionalHostnameListResponse);
}

M

mackongOP•12/17/25, 11:29 AM

Is there a way to force immediate KV propagation so the edge worker reads the latest value?

Mmackong Is there a way to force immediate KV propagation so the edge worker reads the la...

H

Hello, I’m Allie!•12/17/25, 4:57 PM

No

Mmackong Is there a way to force immediate KV propagation so the edge worker reads the la...

T

thomasgauvin•12/17/25, 9:38 PM

@mackong why do you want this? please share you use case so we can understand how to prioritize

Tthomasgauvin <@1074712113991401543> why do you want this? please share you use case so we can...

M

mackongOP•12/18/25, 2:34 AM

We use KV for application configuration. Most settings rarely change, but for certain data—such as a status change from A to B—workers must see the update immediately.

T

thomasgauvin•12/18/25, 2:42 PM

Can you elaborate on which type of your configs need changes reflected immediately? You can DM me as well if you prefer

Tthomasgauvin Can you elaborate on which type of your configs need changes reflected immediate...

M

mackongOP•12/19/25, 5:19 AM

Our product is paid. We store each user’s overdue status in KV; if they’re overdue, we return an error. After a user pays, the status is updated in central storage and synced to KV, but workers may read a stale overdue value and still return an error. We need a way for workers to read the latest status so users can access the product immediately after payment.

M

Mrxbox98•12/19/25, 6:24 AM

On the KV

getWithMetadata

getWithMetadata

function, what are the possible return values for the

cacheStatus

cacheStatus

property. I don't see any info on it here: https://developers.cloudflare.com/kv/api/read-key-value-pairs/#getwithmetadata-method

Cloudflare Docs

Read key-value pairs

To get the value for a given key, call the get() method of the KV binding on any KV namespace you have bound to your Worker code:

Mmackong Our product is paid. We store each user’s overdue status in KV; if they’re overd...

P

PhoenixSpace•12/19/25, 2:01 PM

If a 60 second TTL is too long this sounds like an eventually consistent store is the wrong product over something immediately consistent like D1 or a DO

T

thomasgauvin•12/19/25, 2:43 PM

Our product is paid. We store each

PPhoenixSpace If a 60 second TTL is too long this sounds like an eventually consistent store i...

T

thomasgauvin•12/19/25, 2:44 PM

Configuration of this type is something we aim to support, and we are looking into providing more controls over eventual consistency. We will have more to share in the new year

R

Ruz•12/22/25, 2:10 PM

hey, I recently got an email that I surpassed my KV worker limit for the free tier, but when checking the usage on my dashboard they weren't showing any numbers within the metrics, is this a known bug or is there another way to see specific kv worker details?

Hi, I’m getting a 429 error when writing to Workers KV via the HTTP API. The docs say the Enterprise

Similar Threads

Similar Threads

Similar Threads