quick question about workers, if I use all 100,000 requests of the free plan, the worker will just s
quick question about workers, if I use all 100,000 requests of the free plan, the worker will just stop working until the daily reset, right?
Cit can take a bit for it to stop working/fail espec if they all come in at once, and the exact behavior depends on the worker route settings (can make it fail open -> requests straight to origin) or fail closed (worker custom domains just do this). If the question is just about billing you won't get charged for more or forced to upgrade or anything, it'll just eventually stop working
LOk thanks
Lis there a way to upgrade to the $5/month plan for the 300.000 daily requests but disable billing for requests past the 300.000?
CWorkers Paid includes 10 mil requests for free, it's not broken down daily or anything like that
CYou can setup Alerts for when you go above a specific threshold, but no hard cutoffs
Lso 10 million requests per month?
C10 million included per month
+$0.30 per additional million and then you get billed for cpu time as well (and there's an included tier of that)
https://developers.cloudflare.com/workers/platform/pricing/
+$0.30 per additional million and then you get billed for cpu time as well (and there's an included tier of that)
https://developers.cloudflare.com/workers/platform/pricing/
Lhmmm ok thanks for the info
Crespond with 429/specific status code and you can see it in web traffic analytics (pro or higher)
CI have mine set to 1,500 per minute (per key) and I have some cases where I'm seeing 10x that (15k per minute - assumed to be per key)Is the traffic distributed? Rate limiter is per Cloudflare location/pop
CUnder your website/zone "Analytics & Logs" -> Traffic. You'd have to be sending all the requests through that zone though, wouldn't see any if they were direct to workers.dev
CI mean, is the incoming traffic distributed?
CWorkers by default run in every cloudflare location everywhere
CIf you get 1499 requests in EWR/New York and 1499 in LHR/London and 1499 in SLC/Salt Lake City, your rate limiter wouldn't be exceeded
CYou could use a Durable Object as a rate limiter then per key to have globally consistent limits
CWeb Analytics isn't what you want, that's more Google Analytics type /client-side analytics
CWeb Traffic Analytics is server-side and under each website "Analytics & Logs" -> Traffic
CCall you have to do is have Pro or higher and send the traffic through that website on a worker custom domain or route, and you can see response codes on there:
CIf you wanted more granular/user specific stuff, you send metrics to Analytics Engine: https://developers.cloudflare.com/analytics/analytics-engine/, with the index being some id for the api key and the double/value being blocked or not, and then you could filter off that. You could also just send only rate-limited response metrics, up to you
Care your requests going through that website?
Cif you go under your worker, logs -> real-time logs, you can tail and see the request url
Chow is your worker being requested, is what matters
Falso running into the 5mb sourcemap limit. why is this limit so low
Fwe should have an option to upload source into R2. happy to pay for the space
Tany log analytics tools that native support by cloudflare? now I've setup the R2 and logpush, any suggestions?
CDoes anyone know if there are any stats around parse times for workers as they get larger? Just interested is there a tipping point or random stats
HParsing time should generally never be high enough to be noticeable, though startup time does sometimes get high enough to crash the Worker
Smy worker reports the wrong time, somehow, if i use toLocaleString.
for timestamp 1720179195419 i should get, with locale "de-DE", something like 13:33, but it's 11:33 in my worker
for timestamp 1720179195419 i should get, with locale "de-DE", something like 13:33, but it's 11:33 in my worker
Spls tell me i dont have to use the intl api
Si have to use the intl api
Cbumping this for anyone who is searching for details on "consuming from multiple queues in a single worker"
VThe rate limit binding doesn't seem to work very well, i know it's in beta but i can get a lot more than the limit through before it starts to return false.
I have a remix pages app, that binds to a service worker that binds to a ratelimit to get around pages not working with rate limits directly i wonder if that has anything to do with it or if that's the general experience. (limit 3, period 60)
I have a remix pages app, that binds to a service worker that binds to a ratelimit to get around pages not working with rate limits directly i wonder if that has anything to do with it or if that's the general experience. (limit 3, period 60)
Mdo workers literally just not work now?
Mwith wrangler
AHas there been any further news about (Durable) Workflows that was announced in the Developer Week in April?
CWhat do you mean by not work?
