WExceeding at 10ms sounds like you're on the free plan
WAre you still subscribed to Workers Paid?
YI would happily subscribe to the paid plan but what I fail to understand is when I check the old logs (3 days back) I can see that this worker had cpu time averaging around 160-200ms (and rare cases where it was sub 4s) and the request never failed and this app has been running for a good few months now(?) why has this suddenly started to happen is this something recently being imposed?
YI just made another request which as per the logs took 229ms cpu time and stil wasn't blocked
W?link
SPlease use the /link command to authenticate with your Cloudflare account and link it to your Discord user. This helps Cloudflare employees access your details more quickly and provide support. It also makes future support requests easier, since your account will already be linked.
Wcan you /link and give me your worker name?
WIt's possible you were just generally below the time limit and were ok, the CPU time is bucketed. So you can go over but once the bucket is empty, you'll be limited at the normal limit
Yi have linked my account, worker name is "onedegree-api". is there a help page that mentions this bucketed limit for free or paid plans.
WEach isolate has some built-in flexibility to allow for cases where your Worker infrequently runs over the configured limit. If your Worker starts hitting the limit consistently, its execution will be terminated according to the limit configured.
