So worker only charge by request and CPU time in metric now? The rest indicator for reference only ?

Kkamama So worker only charge by request and CPU time in metric now? The rest indicator ...

Correct, if you are not using Durable Objects then you will only be charged based on requests and CPU time, not wall time.

kamamaOP•4/5/25, 2:45 AM

Wow, then SSE is a good solution now

andifined.dev•4/5/25, 6:23 AM

Hello!

I‘m looking for a way to process Videos using workers or workflows. In Detail my goal is to cut an image out of a video that’s stored in R2 every 1 second and persist it in R2 again. I thought maybe media transformations would work, but I don‘t Thank it fits my needs quite well because of caching and requiring an URL to work. Are there any other approches for that?

く

くもりにくもったクラウドサービスlocaler•4/5/25, 2:35 PM

I'm trying to use Argon2 with SvelteKit (on Cloudflare Pages) and Argon2 WASM (on Cloudflare Workers) via service bindings,
but I keep getting the error: "Worker exceeded CPU time limit."
Is there any way to fix or work around this issue?

く

くもりにくもったクラウドサービスlocaler•4/5/25, 2:37 PM

Do I need to upgrade to a paid plan to make it work?

seflanka•4/5/25, 6:54 PM

hello

Avi•4/6/25, 6:37 AM

is pages officially deprecated yet?

James•4/6/25, 12:11 PM

Not officially yet, and I’d be surprised if they ever do, but I would recommend Assets for new projects. Pages is already lagging behind in terms of new bindings its supports, and you’ll have a better experience with Assets.

Silvan•4/6/25, 2:13 PM

I still wish we had a better way of binding services like DOs to meta frameworks without a monorepo :/

Often you just dont have “access” to the server entrypoint due to it being generated

Silvan•4/6/25, 2:18 PM

unless someone has a cool solution. in case of sveltekit you have this

main = ".svelte-kit/cloudflare/_worker.js

main = ".svelte-kit/cloudflare/_worker.js

and i really haven’t found a way to make it include a DO class inside that file

SSilvan I still wish we had a better way of binding services like DOs to meta frameworks...

DaniFoldi•4/6/25, 2:48 PM

I'd actually recommend deploying them separately, wherever it makes sense:

if you use websockets, a new deployment will disconnect all clients, so you'll get a spike of reconnects - and it could be unnecessary if you didn't actually change your websocket handling DO code

DDaniFoldi I'd actually recommend deploying them separately, wherever it makes sense: if y...

Silvan•4/6/25, 2:51 PM

oh thats actually a very valid point :thinkies:

Even do having a DO repo seems silly but i dont think you can have a monorepo at all then if you use git for deployments due to it triggering both if they both look at the same repo

Silvan•4/6/25, 2:51 PM

but good input thanks!

Silvan•4/6/25, 2:52 PM

(also dev experience suffers a bit from it but cant have it all)

SSilvan (also dev experience suffers a bit from it but cant have it all)

DaniFoldi•4/6/25, 2:54 PM

If it's in the same repo, you can define a script that starts

wrangler dev

wrangler dev

with all of the workers

DDaniFoldi If it's in the same repo, you can define a script that starts `wrangler dev` wit...

Silvan•4/6/25, 2:57 PM

yea im aware but that would enforce deploying the DO over the cli if im not completely off here? else i dont see how they could be deployed separate from each other

DaniFoldi•4/6/25, 2:59 PM

you can think of Durable Objects as separate workers, and as long as your code remains compatible (since you can't deploy at the exact same second, building in some compatibility is always best), you can deploy a new version to only one or the other
yes, workers CI would trigger on both of them if you push to the repo by default, but you can check https://developers.cloudflare.com/workers/ci-cd/builds/build-watch-paths/ on how to set up watch paths so they only run if the relevant code is changed

Cloudflare Docs

Build watch paths · Cloudflare Workers docs

Reduce compute for your monorepo by specifying paths for Workers Builds to skip

Silvan•4/6/25, 3:01 PM

oh wow thats the point of watch paths omg learning something new everyday! thanks a lot

Kotkoroid•4/6/25, 3:43 PM

Hi, should I be putting

worker-configuration.d.ts

worker-configuration.d.ts

into

compilerOptions.types

compilerOptions.types

include

include

? Docs recommend the first option but I'm getting:
error TS2688: Cannot find type definition file for 'proxy/gateway/worker-configuration.d.ts'.
│ The file is in the program because:
│ Entry point of type library 'proxy/gateway/worker-configuration.d.ts' specified in compilerOptions

The file exists.

tsconfig:
{
"compilerOptions": {
"target": "ESNext",
"module": "ESNext",
"moduleResolution": "Bundler",
"strict": true,
"skipLibCheck": true,
"lib": ["ESNext"],
"types": [
"@cloudflare/workers-types",
"./proxy/gateway/worker-configuration.d.ts"
]
}
}

No problem when added to

include

include

but I think that's not where

d.ts

d.ts

should be?

Deltachaos•4/7/25, 12:00 PM

reagrding the free tier limits:
it says 10ms cpu time for workers. Some of my requests have something around 77ms cpu time (and worked). Can i assume that this will not work reliably? Or is the average cpu time relevant for the limits? And if so, how do crons play into this?

For example i have a cron that accidentally was spending 1,329ms cpu time before it got interupted. Now following crons are failing with something like

Exception in callback <_asyncio.TaskStepMethWrapper object at 0x1a38940>()

Exception in callback <_asyncio.TaskStepMethWrapper object at 0x1a38940>()

with 0ms cpu time. Can i assume that they are throttled? How long do such throttles last?

hffmnn_•4/7/25, 12:37 PM

Hi. I am running into the "I need multiple fallback origin" problem. That means that I have multiple apps aka. workers that need to be available under different custom, external hostnames. So I would try out the proxy worker workaround aka. the fallback origin will point to a worker that routes to other workers internally. Does anyone know about a write-up that sums up problems with that approach?

dave•4/7/25, 6:14 PM

Is there something like

cf-ray

cf-ray

but for Cron Workers?

dave•4/7/25, 6:14 PM

Trying to find a unique value that I should be logging for analytics.

Ddave Is there something like `cf-ray` but for Cron Workers?

Hard@Work•4/7/25, 6:54 PM

What Leo said, or just generate a UUID/nanoid?

LordSilver•4/8/25, 7:22 AM

So an "Agent" is just a Worker that imports the agents module?

Silvan•4/8/25, 10:40 AM

Its rather a "Class" that extends a Durable Object

Ricky U•4/8/25, 1:54 PM

Pages functions is using an older wrangler version, can i change the wrangler to latest in env var?

Ricky U•4/8/25, 1:55 PM

Found Functions directory at /functions. Uploading.
20:23:27.201     ⛅️ wrangler 3.101.0

Found Functions directory at /functions. Uploading.
20:23:27.201     ⛅️ wrangler 3.101.0

Latest i belive is v4.x no?

SSilvan Its rather a "Class" that extends a Durable Object

LordSilver•4/8/25, 2:17 PM

what

LordSilver•4/8/25, 2:17 PM

A DO is a special Worker

LordSilver•4/8/25, 2:18 PM

But I don't think importing agents into your Worker makes it a DO

LordSilver•4/8/25, 2:18 PM

or you are saying agents actually is a separate worker

LordSilver•4/8/25, 2:18 PM

like the puppeteer library that connects your Worker to a machine with Chrome + Puppeteer installed

LordSilver•4/8/25, 2:18 PM

the browser api or whatever that's called

LordSilver•4/8/25, 2:19 PM

really weird stuff anyway

LordSilver•4/8/25, 2:19 PM

importing libs in Workers is like plugging microservices

LLordSilver what

Silvan•4/8/25, 2:20 PM

LordSilver•4/8/25, 2:21 PM

Server is Agent?

Silvan•4/8/25, 2:21 PM

Im just saying Agents are wrapper around Durable Objects to make your life easier

gruntlord6•4/8/25, 3:14 PM

any idea why this happens? not a huge deal but the latest build shows workers build and all the others show wrangler.

They were all using workers builds so I find it odd that it changes after a new deployment

Kotkoroid•4/8/25, 4:46 PM

If I do this for Workers, should I then use vite devvite dev instead of

wrangler dev

wrangler dev

Mozzy•4/8/25, 4:47 PM

It would be nice to know the progress of https://developers.cloudflare.com/pages/platform/known-issues/#delete-a-project-with-a-high-number-of-deployments, since a few more people are probably going to be deleting Pages projects

DiamondDragon•4/8/25, 4:53 PM

shoutout for adding tanstack start documentation on workers soon

MMozzy It would be nice to know the progress of <https://developers.cloudflare.com/page...

Chaika•4/8/25, 4:55 PM

considering

Cloudflare Pages will continue to be supported, but, going forward, all of our investment, optimizations, and feature work will be dedicated to improving Workers.

not sure that's ever going to be fixed

datacenterdude•4/8/25, 5:31 PM

In Build Configuration, I've got my swaggerUI kit and index.html in a /api subdir in the repo. What's the proper syntax to use there in the Build OutputBuild Output field? I see the leading slash before the field, but does it need any kind of ./api/./api/ or anything special or simply

api

api

CChaika considering > Cloudflare Pages will continue to be supported, but, going for...

Mozzy•4/8/25, 5:49 PM

sad

datacenterdude•4/8/25, 5:56 PM

I mean, I get it... I could see the functionality of Pages just getting folded into Workers (if that's the idea?)

Ddatacenterdude In Build Configuration, I've got my swaggerUI kit and index.html in a /api subdi...

Walshy•4/8/25, 5:59 PM

just

api

api

jason•4/8/25, 6:04 PM

I'm migrating Pages to Workers.

On Pages, I'd call DEPLOY_HOOKDEPLOY_HOOK after Github Actions passed tests successfully.

For workers, I don't see deploy hooks.

Is it suggested to call npx wrangler deploynpx wrangler deploy directly from CI?

I'm a little concerned about not catching incompatibilities due to the Github Actions CI runtime being different from Cloudflare's build image

So worker only charge by request and CPU time in metric now? The rest indicator for reference only ?

Similar Threads

Similar Threads

Similar Threads