Paid plan not applied to my opennextjs-cloudflare Worker
Hi, I’m on a Workers Paid plan, but my project deployed with opennextjs-cloudflare still behaves as if it’s on the Free tier.
Other Workers in the same account work fine, but only the opennextjs-cloudflare-deployed project shows “Assets: Free” in the dashboard (see attached screenshot) — and it seems to be stuck with the Free-tier 10 ms CPU limit.
Could you please check if my account or this Worker isn’t correctly marked as “Paid”?
Any help would be greatly appreciated. This causes a lot of errors in production...
8 Replies
IIRC it says Assets: Free because Asset serving is free, regardless of Free/Paid Workers Plan Status
Thanks! That makes sense — so the “1102 – Worker exceeded CPU time limit” errors aren’t caused by the plan itself.
I can see from the dashboard metrics that the CPU time per request is very low, so the number of 1102 errors is confusing.
It seems something else is triggering them — I’ll dig deeper and check again.
Note too that you can apply your own CPU time limits to a Worker on Paid, so that might be what is happening
I just tried setting the limit to 5000 ms, but the error rate is still around 8.5%.
So it doesn’t seem to be resolved yet😭
Maybe give it a sec? Metrics don’t update instantly
Ah got it, thanks! I’ll wait a bit and see if the metrics update.
Still seeing errors unfortunately...😰
Seems like there’s a deeper issue, I’ll keep investigating.
Just wanted to follow up — the issue is resolved.
It turned out that almost all of the exceededCpu errors were coming from AI crawlers.
After blocking them, the errors stopped.
I’m still not entirely sure why those bot requests were triggering CPU limit errors though the logs showed very low cpuTimeMs (around 10 ms) for each one.