Cloudflare Developers•3mo ago

Seems like they fixed that now https://developers.cloudflare.com/changelog/2025-02-20-synchronous-up

Seems like they fixed that now https://developers.cloudflare.com/changelog/2025-02-20-synchronous-uploads/

Cloudflare Docs

Workers for Platforms - Instant dispatch for newly created User Wor...

Newly uploaded user Worker scripts are now immediately available for dispatch upon a successful API response.

PepsOP•10/8/25, 10:08 PM

huh actually no, that's from february this year

PepsOP•10/8/25, 10:08 PM

https://github.com/cloudflare/cloudflare-docs/pull/20117#issuecomment-3383376798

PepsOP•10/8/25, 10:08 PM

think there's been some miscommunication

PepsOP•10/8/25, 10:09 PM

or they really just shipped that now and had the docs/announcement PR ready since feb lol

Prydar•10/9/25, 1:08 PM

built my first WfP tests today (based on getting started docs) - some observations - clicking on Dispatcher on dashboard errors out completely. Tags are cool, but no way to add/edit them with web gui. Very little observability of user workers. I'm clicking/reloading the demo "hello world" and the stats aren't updating on the user worker, but that could just be a delay thing.

Rafflesia•10/10/25, 2:38 AM

workers for platforms is fine but the dashboard UI for namespaces is pretty bad

Rafflesia•10/10/25, 2:38 AM

the regular workers UI in the dashboard is really nice, you can sort by requests and everything

Rafflesia•10/10/25, 2:38 AM

I really wish that same UI was in workers for platforms

PPeps Seems like they fixed that now https://developers.cloudflare.com/changelog/2025-...

Vlad Lykhonis•10/10/25, 4:59 AM

Interesting. I still see the issue, but will double check now. There is built in retry mechanism also in there, but it seems to fail regardless.

PPeps https://github.com/cloudflare/cloudflare-docs/pull/20117#issuecomment-3383376798

Vlad Lykhonis•10/10/25, 5:01 AM

There was a comment not to forget to update date hehe

RRafflesia I really wish that same UI was in workers for platforms

Vlad Lykhonis•10/10/25, 5:02 AM

It is the same ui. When you deploy wfp enable observability in its settings. It will show up on the main ui

Rafflesia•10/10/25, 5:09 AM

as in its possible to get this UI

Rafflesia•10/10/25, 5:09 AM

for this?

Rafflesia•10/10/25, 5:09 AM

if so how do I enable observability?

RRafflesia as in its possible to get this UI

Vlad Lykhonis•10/10/25, 5:16 AM

I’m talking about observability page specifically.

To enable it for wfp specify it in metadata/settings when creating one worker or update it https://developers.cloudflare.com/api/resources/workers_for_platforms/subresources/dispatch/subresources/namespaces/subresources/scripts/methods/update/

Cloudflare API | Workers For Platforms › Dispatch › Namespaces ...

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

VVlad Lykhonis On this page: https://developers.cloudflare.com/cloudflare-for-platforms/workers...

Vlad Lykhonis•10/10/25, 5:18 AM

I have a question on limits around workers for platforms

Can someone clarify whether we have account limits of DOs and workflows applied when using within wfp?

Rafflesia•10/10/25, 5:19 AM

^^ Same question here but also with D1

RRafflesia ^^ Same question here but also with D1

Vlad Lykhonis•10/10/25, 5:20 AM

Limits apply for D1 (50k per account).

Rafflesia•10/10/25, 5:20 AM

Sean Dubb•10/10/25, 7:23 PM

Hi all -- trying to understand the WfP pricing. It says 1000 Scripts are included and then $0.02/Script afterwards. Is that per month? Or is that the one-time price of deploying one script?

PepsOP•10/10/25, 7:32 PM

monthly

PepsOP•10/10/25, 7:32 PM

there's an example pricing calculation at the bottom which confirms that:
https://developers.cloudflare.com/cloudflare-for-platforms/workers-for-platforms/platform/pricing/#example-pricing

Cloudflare Docs

Pricing

The Workers for Platforms Paid plan is $25 monthly. Workers for Platforms can be purchased through the Cloudflare dashboard.

Sean Dubb•10/10/25, 7:37 PM

I see, thank you.

Sean Dubb•10/10/25, 7:38 PM

Am I understanding correctly that any bundle of user code that my app deploys will cost $0.02/month even when completely idle?

Sean Dubb•10/10/25, 7:41 PM

I guess that would rule out Cloudflare as an infrastructure provider for a platform that wants to give its users the Vercel-like UX of deploying preview environments that stay up indefinitely

Sean Dubb•10/10/25, 7:41 PM

But let me know if I've missed anything

Doan | Full-Stack Developer•10/12/25, 2:45 PM

Hello guys.

Original message was deleted

Sean Dubb•10/12/25, 3:13 PM

Hopefully. I’d much rather pay to store my users’ bundles elsewhere.

$0.02/month is really very expensive compared to alternatives for this use case.

PepsOP•10/12/25, 3:14 PM

you could always put some custom logic on top that removes inactive workers and then cold-boots them in once visited again

PepsOP•10/12/25, 3:15 PM

not the most ideal, but might work in some cases where there's a lot of inactive workers

Sean Dubb•10/12/25, 3:17 PM

Yeah that’s a good idea. I’ve got something like that set up with Sandboxes right now, which I’m able to spin up pretty quick

Sean Dubb•10/12/25, 3:17 PM

How long does it take to deploy a fresh wfp worker?

Sean Dubb•10/14/25, 3:15 PM

Anyone know if the scripts billing is prorated? As-in, if I deploy a WfP script for 3 days, then delete it, am I charged roughly

(3/30)*0.02 = $0.002

(3/30)*0.02 = $0.002

? Or will they charge for a full $0.02 for that script for that month?

Sean Dubb•10/14/25, 3:15 PM

The pricing page is a little ambiguous on Script pricing

MTTM•10/18/25, 11:19 PM

@Peps

MMTTM @Peps

PepsOP•10/18/25, 11:28 PM

What are you randomly pinging me for...?

MMTTM @Peps

Hello, I’m Allie!•10/18/25, 11:29 PM

?pings

SuperHelpflare•10/18/25, 11:29 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.

King Kazu•10/20/25, 6:43 PM

what is best practice for calculating hash for files in manifest?

King Kazu•10/20/25, 6:44 PM

there is little docs on if I need to match the hashing used by cloudflare, or if it doesnt matter as long as my hashing strategy is consistent in my application layer

King Kazu•10/20/25, 10:09 PM

im also facing issues when I start an asset upload for a new worker, I am getting empty array back the asset upload....

📝 Created asset manifest
manifest {
  "/src/test.ts": {
    "hash": "4ebde158676b318f31b855c7908e31fa",
    "size": 1903
  }
}
📤 Starting asset upload session...
assetUpload.create {
  jwt: '*********',
  buckets: []
}

📝 Created asset manifest
manifest {
  "/src/test.ts": {
    "hash": "4ebde158676b318f31b855c7908e31fa",
    "size": 1903
  }
}
📤 Starting asset upload session...
assetUpload.create {
  jwt: '*********',
  buckets: []
}

Robert•10/21/25, 5:13 PM

what usage can be re-billed under WFP? we are building a no-code platform for worker AI + Gateway + autorag. Will that be able to benefit from WFP? different instances will need their own AI interference, own autorag folders, and own websites to index, to name a few.

Prydar•10/23/25, 6:58 PM

bleh, no secret setting via wrangler cli with a user worker? What the heck?

Kaylee•11/3/25, 9:43 AM

Is it possible to have an API key that is limited to a specific WFP namespace?

ALECKS•11/13/25, 3:01 AM

Are Dynamic Worker Loaders supposed to be a light weight version of WfP?
I see that WfP supports more things, like providing storage, and more control over in/egress.. but strictly speaking from an untrusted-code execution point of view, are there any fundamental differences between the two? If I just want to let my customers write some code snippets that extend my product, am I missing on anything by using DWL vs WfP?

dandoen•11/14/25, 9:38 AM

hi team, my outbound worker is not getting called. what am i missing?

i have defined the "outbound worker" and attached to my dispatch namespace, and am executing user workers through the dispatch namespace with the outbound configuration as per docs, but i am not seeing the outbound worker get invoked. what am i missing? my configurations:

[[env.production.dispatch_namespaces]]
binding = "USER_WORKER_DISPATCHER"
namespace = "custom-tools-workers"
outbound = {service = "outbound-proxy", parameters = ["params_object"]}

[[env.production.dispatch_namespaces]]
binding = "USER_WORKER_DISPATCHER"
namespace = "custom-tools-workers"
outbound = {service = "outbound-proxy", parameters = ["params_object"]}

(in env local, i have the same with remote = true – my outbound worker

outbound-proxy

outbound-proxy

does not have envs)

i can see this picked up as both wrangler locally and the dashboard show the outbound proxy:

env.USER_WORKER_DISPATCHER              Dispatch Namespace
  custom-tools-workers (outbound -> outbound-proxy)

env.USER_WORKER_DISPATCHER              Dispatch Namespace
  custom-tools-workers (outbound -> outbound-proxy)

my user workers are deployed to the dispatch namespace using

PUT https://api.cloudflare.com/client/v4/accounts/${CLOUDFLARE_ACCOUNT_ID}/workers/dispatch/namespaces/${NAMESPACE_NAME}/scripts/${scriptName}

PUT https://api.cloudflare.com/client/v4/accounts/${CLOUDFLARE_ACCOUNT_ID}/workers/dispatch/namespaces/${NAMESPACE_NAME}/scripts/${scriptName}

and are executed through the dispatcher:

const userWorker = env.USER_WORKER_DISPATCHER.get(
  scriptName,
  {},
  {
    outbound: {
      params_object: {
        tenantId,
      },
    },
  },
);

const response = await userWorker.fetch('https://dummy-url.local', {
  method: 'POST',
  headers: {
    'Content-Type': 'application/json',
  },
  body: JSON.stringify(testData),
});

const userWorker = env.USER_WORKER_DISPATCHER.get(
  scriptName,
  {},
  {
    outbound: {
      params_object: {
        tenantId,
      },
    },
  },
);

const response = await userWorker.fetch('https://dummy-url.local', {
  method: 'POST',
  headers: {
    'Content-Type': 'application/json',
  },
  body: JSON.stringify(testData),
});

but i'm not seeing the fetch handler of the outbound worker get called.

any help would be appreciated. thanks!

Ddandoen hi team, my outbound worker is not getting called. what am i missing? i have de...

dandoen•11/14/25, 1:23 PM

i have created a minimal repro repo:
https://github.com/dandoen/outbound-worker-minimal-repro/tree/main

@Vero would appreciate any help on this, lost a whole week on this

GitHub

GitHub - dandoen/outbound-worker-minimal-repro

Contribute to dandoen/outbound-worker-minimal-repro development by creating an account on GitHub.

dandoen•11/14/25, 3:21 PM

at this point im starting to think no one is using outbound workers/dispatch namespace. don't see any usage of it https://github.com/search?q=dispatch_namespaces+language%3ATOML&type=code&p=2&l=TOML

Walshy•11/14/25, 11:30 PM

Defiitely usage

dandoen•11/15/25, 7:47 AM

ok, phew! do you see anything off with my implementation @Walshy | DevPlat EE ?

📝 Created asset manifest manifest { "/src/test.ts": { "hash": "4ebde158676b318f31b855c7908e31fa", "size": 1903 } } 📤 Starting asset upload session... assetUpload.create { jwt: '*********', buckets: [] }

const userWorker = env.USER_WORKER_DISPATCHER.get( scriptName, {}, { outbound: { params_object: { tenantId, }, }, }, ); const response = await userWorker.fetch('https://dummy-url.local', { method: 'POST', headers: { 'Content-Type': 'application/json', }, body: JSON.stringify(testData), });

Seems like they fixed that now https://developers.cloudflare.com/changelog/2025-02-20-synchronous-up

Similar Threads