Gah, yes, not cloudflare cache. I should've checked that.
Kyea
Kmakes sense
IHave you added the binding in the local command?
G@kavinplays is the cloudflare cache counting as a worker invocation still (or still invoking the worker) documented anywhere?
Gi'm putting together a feature request/feedback and just wanted to cite things if possible
IAny request to a path where it runs. All requests to the site if you have a
_worker.js/functions
JDoes functions usage count towards the regular workers usage?
INo, it's separate. 100k/day for free now during the beta. You can do 100k/day for each for free. Workers can be increased for a price.
Jah cool
IThat doesn't sound correct... What is the path you are deploying to? Can you share a screenshot of the
/functionsit's probably _worker.js, see above about how a few of us have talked about this and how to maybe do some better work there in the future around static assets.
Git actually punishes you for doing things like route or bundle splitting that things like sveltekit do
Goh that's different I suppose.
IIt looks correct to me, I did notice some weird count of invocations myself, but it was a
_worker.jsI was about to ping @gregbrimble, but I see him typing ahah
GWe’re aware of this issue on Windows. I’ll be trying to fix next week 
AHe's always watching! 
IEven on a Saturday night 
Acovid 
Ahehe me too
IBut Greg is in the UK, if I remember correctly. So it's 10pm on the Saturday. We are going OT.
Aswitching between usc and bama rn
GYeah, we talked about it before, but any project with any functions stuff (anything in the functions directory or an _worker.js) make every request on that project count as an invocation.
IOh, wow. Didn't know that. I guess it needs to parse the paths...
GWe’re figuring out if we can get smarter about that when we come out of beta, but yes, even static assets without any matching route will count as an invocation.
GJust get in touch if it’s an issue and we’ll be more than happy to up that 100k limit.
GFor a little behind-the-scenes, what we’re doing at the moment is just compiling the functions directory into an _worker.js.
GAnd that gets invoked for all incoming requests.
G@gregbrimble I sent a support req, we're about 99% sure of migrating almost all of our backend over to CF + CF pages and moving a bunch more into durable objects, we're super thrilled but getting hit hard by that req limit at the moment. looking at doing some more clever things with setting up another service, but need service bindings too. no worries today, but I'm working on machinery.
GAH!
JI'd think that only requests to matching routes would count as an invocation, would this behavior change when pages functions leaves beta?
