I think what confused me was the splitting it into two columns. Really it's 1 tier but with 1mil inc
I think what confused me was the splitting it into two columns. Really it's 1 tier but with 1mil inclusive operations
SYup! Should be renamed to "Included with subscription" or something like that
PHello! QQ, anybody here kjnows how to setup a scheduler worker trigger for it to run every 5 seconds? Thanks
CWorkers CRON/Scheduled Handler can only go down to per minute in granularity. If you need anything more specific, you'd need to use Durable Object Alarms or something else
Pgot it, i will look into that! Thanks
Jfeel like that's all going to be changing with the new RPC stuff..
Jlooking forward to some people making some videos / content about it
LIf you really want to dive deeper into that topic, I'd recommend some type of Microservices like one Worker (Service) for each set of Features
LThe new RPC Stuff will open up a lot of new Possibilities. You could have for example some kind of Worker before every Microservice that'll just call the Microservice via RPC and handle all the global Logic instead of adding a Set of global logic to every Micro Service
AI’ve noticed since the rollout of versions that I have no history for some metrics in the dashboard for workers that have had a deployment since the release of versions. Just a hockey stick for the latest version and nothing before that. Known issue?
AAnd I have “All deployed versions” selected. Maybe it’s just isolated to the Requests section, but I thought I saw it in several metrics earlier today.
DHi, so CF doesn't store worker logs? Looking at the docs I can only do real-time (tail them or dashboard tail) or create another worker? That then stores them whereever we have a DB to write to? Is this right? CF doesn't store logs / I can't view historical logs?
Jcorrect, you'll need to send them to a 3rd party service.. I've been experimenting with baselime recently
Dmaybe it's a paid upgrade?
D@johtso thanks! ok wow. like wow. how can this be?
D"oh it be" - Seinfeld...
Dwell..... shyt.
JI think it's the nature of cloudflare's offering, it's very stripped down
Dgotcha
D"very"
Dalright, i guess i'll write my own logger send to a DB, etc... jeez
Dthanks!!
Jthey did recently acquire baselime, so hopefully some more tightly integrated instrumentation soon
Jbut yeah.. honeycomb and baselime both have a generous free tier, you send data to them using an opentelemetry library
Dthat's too bad ha... i just built a much more advanced visualization platform.
Dbut clearly they need a logging featureset
Dyep, OT is excellent
Dwait till they see my observability app 
ironically, now i'm plugging my own logging into it and i just assumed i can go fetch some logs like CloudWatch
ironically, now i'm plugging my own logging into it and i just assumed i can go fetch some logs like CloudWatchDthanks a ton @johtso
Blmao whats this
D@bun yep i just saw that
JSeems odd that you can't give a Cron trigger a name, and instead you have to match on the actual Cron expression.. basically hard coding it in 2 places
Bwhy do you need to match cron triggers though?
JIf you have multiple triggers that do different things
Bwas about to type the same thing
BI'd love to have them decoupled
Bseems like such an easy lift too lol
BI just want my code to care about names, and my wrangler.toml can care about the expressions
Bmakes it easier / cleaner to test too
EDoes anyone from Cloudflare know if there are plans to change this constraint? “For Workers fronted by Cloudflare Access, the Cache API is not currently available.”
Dthat's not true, tbh not sure what it's referring to. I use the Cache API all the time in my Workers that are behind Access.
EInteresting. I am unable to use the Cache API in a worker protected by access. I can try to use it and it throws no errors but nothing gets stored in the Cache. I’ve had to resort to relying of the normal fetch caching but for my use case that is not ideal.