Any requests that are like *critically* urgent I might be able to accelerate.
Any requests that are like critically urgent I might be able to accelerate.
I(no promises haha)
SWhoa I would love to get some hand on help with workers. 
I'm trying to move some code from client side to functions.
I'm trying to move some code from client side to functions.
SThanks man, you're extremely helpful. Nothing urgent regarding plan limits. Only urgency for now is actually implementing the functions. 
EYou cannot yet 
SWhat's a DO class?
SDoes that mean you can DOs via functions?
JYou can't define them in functions, but you can use them if you create them elsewhere. Not a great flow, but you can get it working if you need to
SOh! Didn't expect that 
JI don't believe so. You could use a Worker and
fetch
IYeah, you'll need to create a Worker to call your Function then, Functions can't do Cron Triggers yet
Cthat looks like it should work fine. What OS are you on?
IHmm... can you confirm that it's in your root directory and not build output?
KWorker exceeded resource limits means your Worker went over the CPU time limit
KWell, it could also exhaust memory (128MB) but more often than not it's CPU time
KI think it currently reflects the free/bundled models depending on your highest zone plan - so 10ms of CPU time if you have free zones or 50ms if you have any paid zones
Disn't it just dependent the free/pro workers tier?
Ki thought it was based on workers pro tier too
KI've seen both said - Walshy's previous messages indicate it's tied to Workers but others say it's related to the zone plans.
KWill clarify it with people
Kthanks!
Dalways right
KAs for if that'd help, it depends
KIf your app is using more than 10ms but less than 50ms, yeah
KIf it's going above 50ms anyways, it'd likely still get closed down for resource exhaustion
KI don't know if there's anything you can see that'll tell you how much it's using at the moment though - logging & whatnot for Functions is still on the way
AHey there! I keep getting 522 Timed out, I believe it is because my CPU median time is > 10ms (45ms)
AI've read that while in beta the limit is of 100k requests/day (I'm getting 8)
Does changing Workers plan fix this issue with Pages' functions?
Does changing Workers plan fix this issue with Pages' functions?
Awell, actually, it turns out it's not a problem related to CPU time, because accessing the site from *.pages.dev works fine
KCPU time would be a 1102 (Resource Exhaustion) page
AMakes sense
KZone makes me think of two things
KA) you're fetching a Worker on the same custom domain
AI have a misconfiguration on the www. subdomain
K