M
DAlright I’ll do some research thanks
M
AQuick question
From my understanding, calls to service bindings uses the same memory space and thread as the calling worker.
So does calling that service binding count as an invocation against that worker?
Basically what im asking, if I have a worker that always calls a service binding for another worker, and that first worker gets 1 million requests, will I be billed for 1 million reuqests or 2 million requests?
From my understanding, calls to service bindings uses the same memory space and thread as the calling worker.
So does calling that service binding count as an invocation against that worker?
Basically what im asking, if I have a worker that always calls a service binding for another worker, and that first worker gets 1 million requests, will I be billed for 1 million reuqests or 2 million requests?
K2
A:/ ok thanks.
seems a bit excessive to bill that as another invocation when it has to work within the limits of the first invocation IMO
seems a bit excessive to bill that as another invocation when it has to work within the limits of the first invocation IMO
AOn the new standard pricing, you pay for the CPU time anyway, so you aren't charged for the number of requests, so it's not really going to impact your billing
KYou still pay for requests.
AAh yes sorry it's a combo of them both isn't it
KYep.
Bundled = reqs only.
Unbound = reqs + wall time.
Standard (new) = reqs + CPU time.
Bundled = reqs only.
Unbound = reqs + wall time.
Standard (new) = reqs + CPU time.
QAnyone knows if we can disable
Tried deleting the route handlers through the dashboard, but they keep coming back after deploying with wrangler cli
xxxxx.workers.devno fetch handler definedTried deleting the route handlers through the dashboard, but they keep coming back after deploying with wrangler cli
Cworkers_dev = falseiirc having no routes/custom domains at all breaks Quick edit though, or used to. Although Queues wouldn't work with that anyway
Qthanks for the solution and the hint! @Chaika np when it breaks quick edit
MHello ,
I have cloudflare worker , and I want to use WAF custom rule , in the worker
so for example
if (( waf custom rule = example)
do something
how I can do that with cloudflare workers
thanks
I have cloudflare worker , and I want to use WAF custom rule , in the worker
so for example
if (( waf custom rule = example)
do something
how I can do that with cloudflare workers
thanks
KYou'd need to wait for Snippets if you want to run a Worker in response to a WAF rule.
Mwhat you mean by Snippets , can you explain in more details please
KCloudflare Snippets (alpha) provide a flexible way to customize the behavior of your website or application using short pieces of JavaScript code. Use …
Mits still beta and I dont have access to it , is there any other way ??
KNope, Workers currently are always invoked on a given route.
KWhat are you trying to do, invoke a Worker based on a rule or replicate rule logic in a Worker?
Minvoke a Worker based on a WAF rule , (( so I just want the Worker to be triggered only when specific CUSTOM waf rule triggered )) currently its triggered on all (( skip )) waf rules
KYeah, you can only do that with Snippets when they become available.
UWhy do you want to trigger a worker by a WAF rule though? 
Mvpn detection system , currently there are a lot of good bots being detected as vpn , and they got blocked by the worker
Mand I want the worker to not work on (( custom waf rule == known bots ))
KJust to make sure, you are aware that Known Bots means it's a good bot.
Myes I know
KGotcha
Mcurrently my vpn detection system see that most of the good bots as proxy and vpn and they are blocking them
Mso I want to bypass worker if it hit the known bots rule
Mwow ! thats great , by the way what you mean by (( iirc that' the name ))
KThere's
verifiedBotCategory""wow thank you !
Mif (request.cf.verifiedBot) {
// Logic for handling verified bots
// You can choose to bypass certain operations or handle them differently
return fetch(request);
}so it should be something like that , verified and known bots will hit this
// Logic for handling verified bots
// You can choose to bypass certain operations or handle them differently
return fetch(request);
}so it should be something like that , verified and known bots will hit this
SOn the "Overview" page for Workers & Pages, I can see the sum of all my requests and CPU time, etc.
It is not possible, however, to get a breakdown on which Pages projects are using how much unless I click into every project, go to function metrics, and then adjust the timeframe to something other than "last 24 hours"
Is there any way I can view a usage / billing breakdown, even via the API?
It is not possible, however, to get a breakdown on which Pages projects are using how much unless I click into every project, go to function metrics, and then adjust the timeframe to something other than "last 24 hours"
Is there any way I can view a usage / billing breakdown, even via the API?
DIs there an easy way to throttling my subrequests globally?
DI'm using a stupid Azure service that 429's me a lot.
JQueues maybe? You could limit consumer concurrency to a low number
JAssuming you can batch them up into jobs or similar
JI don’t know of any easy way other than that, outside of using durable objects to track and throttle
Dah yep, sounds like queues would be the "easiest" using 
max_concurrency. Dmight be too much of a hassle for this project to rewrite it with queues in mind, but probably should refactor it to do that eventually
CYou can use the GraphQL API to get the metrics https://developers.cloudflare.com/analytics/graphql-api/tutorials/querying-workers-metrics/
<y'know I gotta say,
AssertionError [ERR_ASSERTION]: The expression evaluated to a falsy value: is the most obnoxious, frustrating type of error I've ever seen. This is so unhelpful to the point of making me want to flip a table.<The whole stack trace below just points to the miniflare lib, not my own code, so I have no idea what ever causes this, I have to fumble in the dark like a caveman using ECMAScript 1 in 1998
JCommon issue right now, sorry! There’s a fix up at https://github.com/cloudflare/workers-sdk/pull/4719 which should hopefully land soon
GitHub
Fixes #4715.
What this PR solves / how to test:
Previously, if in a wrangler dev session you called console.log() and threw an unhandled error you'd see an error like [ERR_ASSERTION]: The expre...
What this PR solves / how to test:
Previously, if in a wrangler dev session you called console.log() and threw an unhandled error you'd see an error like [ERR_ASSERTION]: The expre...
<I have an older version of the worker lib, so does it come from elsewhere?
<Can't wait for this to be fixed either way this is really aggravating and I don't like the feeling of frustration that comes with it
JHow old? This was introduced a couple months ago I think
