Yup, my crons are not running since ~4 hours ago
Yup, my crons are not running since ~4 hours ago
AThere was https://www.cloudflarestatus.com/incidents/8qxgw783x9kv which was the dashboard not showing runs, but mine are literally not running as it's not producing output expected
ASun, 18 Aug 2024 12:20:28 - last time mine ran
JAh weird, ours stopped around 18 Aug 14:27 UTC
JWe just tried redeploying it and that seems to have caused it to get triggered a few times
ADeploying my worker now 
JAhh ok it seems like it's dead again
AYeah, mine aren't working even after a deploy, nothing on the status page either 
AI can't raise a proper ticket either as that's restricted to business 
W
JThank you
JSo far mine looks like it's doing okay again
JBut it's hard to tell because the dashboard i'm using has a bit of delay maybe
Jfrom baselime
J
AThanks Walshy!
IAMine just kicked back in 
Dguys I'm using Next.js and want to use cloudflare pages with Puppeteer, which I'm assuming would run on workers instead of lambda functions, do you know a newer tutorial for Next.js, this one seems old:
https://blog.cloudflare.com/running-serverless-puppeteer-workers-durable-objects
https://blog.cloudflare.com/running-serverless-puppeteer-workers-durable-objects
FIf you are blocked by a website that uses Cloudflare, you need to contact the website owner to appeal or investigate the block. Cloudflare is configured by the site owner, and Cloudflare will not overwrite the configuration of any customer. Nobody in this Discord nor any Cloudflare employee will be able to help you. The site owner can investigate why you were blocked through your ray id.
Si see, thanks for helping, and sorry for anything
CThere was no incident then though, only today, and you said you saw the cron events lol, it's very obvious w/ the cron event log if it failed to execute, you can see the skip:
Ithis exact thing happened to me yesterday (and today). except the event logs were successful
Iand no missed event
Cin all of the cron schedule incidents that I have seen, they've always failed to log if they didn't execute
Cso idk, still think your issue is something else sadly/not an easy explanation
.For cron jobs, do they have the same limitations as normal workers? I tried running a script I have (also converting it from python (selenium) to puppeteer) and got a few cpu limit reached errors. What is the limit also?
CShould be up to 30 seconds of CPU Time if scheduled interval is less then an hour, if greater then an hour up to 15 minutes, and 15 minute wall time limit
.What’s wall time limit? Is that from the time the worker fires up to when it stops?
Cyup, something that a normal http worker doesn't have but crons do
.Right ok, and cpu time is calculated by when the worker is “doing something”?
Cyea, cpu time = time spend actually doing work, not time spent waiting on i/o / fetches, etc, and wall time = entire duration including time spent waiting on i/o
.Awesome thanks. Gonna try increasing the cron job time to see if it doesn’t fail due to cpu time. I have a script which scrapes a website but it’s in python and I have no idea how to convert it to puppeteer fully. Guess it’s a time to learn haha. Thanks a lot
.Can you do cronjobs in python by any chance? Or not yet
Clooks like no https://discord.com/channels/595317990191398933/1224715939581530112/1263968631453253664 they have a lot of other limitations rn with no packages anyway
.Oh yes that’s true, wouldn’t be able to install it anyway. Thanks again
Iwasm on workers is not there yet
let alone wasm on workers that ships as expensive of a runtime as python's
let alone wasm on workers that ships as expensive of a runtime as python's
CI don't think there's any big issue with wasm on workers as a whole, plenty of people use Rust workers and such
Most of the issue the team said was just in startup costs and such which they're working on, hopefully we'll see more of that soon
let alone wasm on workers that ships as expensive of a runtime as python'sThe Python runtime is embedded into the workerd/worker runtime (pyodide), so it's just your python code + packages and any overhead of pyodide/python.
Most of the issue the team said was just in startup costs and such which they're working on, hopefully we'll see more of that soon
GHi all, wondering if anyone has ever seen the error
ReferenceError: wasm_438b3227c4b242399e8c7376cf44cc39d16dcd3c is not definedwrangler devprisma@cloudflare/next-on-pagesIt seems related to the prisma query engine, but I'm not exactly sure how to work around it
IThe Python runtime is embedded into the workerd/worker runtime (pyodide), so it's just your python code + packages and any overhead of pyodide/python.ah i did not know that.
i expected python to compile to wasm (including the runtime) and be executed by the wasm runtime.
rust->wasm for workers' boiler (iirc with axum) plate was massive
iirc 300k
iirc workers have a limit of 1M
ignoring actual useful payload that is way too large for comfort
IWorkers have a limit of 1MB only on the free plan. Paid is now 10MB 
Iah
GYeah, this is a blocking issue for me so I'll try and file a GitHub issue with more detail today 
.Does this include it being at an hour interval too? 15 mins cpu time
Cthe exact wording is this
When the schedule interval is less than 1 hour, a Scheduled Worker may run for up to 30 seconds. When the schedule interval is more than 1 hour, a scheduled Worker may run for up to 15 minutes.https://developers.cloudflare.com/workers/platform/limits/
.So which one includes at an hour 
Cso I have no idea because those are both "less then" and "greater then" and not equal to
.Good old docs
Cyou fall into some magical space inbetween both where you get 7.5 minutes /s
Cyea idk, would just have to try and see
