cpu_ms_limit_not_allowed_for_usage_model
Hello, starting from yesterday I started having this error on all my builds, even with code that was passing!
06:17:06.322 ✨ Upload complete!
06:17:08.707 Success: Assets published!
06:17:09.807 Error: Failed to publish your Function. Got error: workers.api.error.cpu_ms_limit_not_allowed_for_usage_model
I see it's related to this changed, which is marked as fixed but I started having the issue after it got fixed: https://www.cloudflarestatus.com/incidents/3q7sg3tpp7qv
Anyone else has the same issue?
11 Replies
Are you still getting it now?
yes last failed build is 6 minutes ago
Thanks for clarifying. Are you on free, or could you create a ticket? The deployment id would also be helpful, and probably the pages.dev as well
?pages-deployment-id
The Pages deployment ID is a unique build identifier.
It's the UUID in the browser bar (for example, a URL would be
dash.cloudflare.com/ACCOUNT_ID/pages/view/PROJECT/DEPLOYMENT_ID where the deployment ID looks something like a398d794-7322-4c97-96d9-40b5140a8d9b).
This ID can help troubleshoot some issues with Pages builds so if you have a failing build make sure you grab that ID for the Pages team to use.I'm still on free for now until I finish dev.
Here's the last deployment id: 809a7ae0-cc12-4353-8008-956279d6dd0e
project: gocollab.pages.dev
Thanks I'll escalate in a sec. Just for my curiosity though, you have just Workers free, right? You've never had Workers paid in the past, and you've never manually set the CPU limit on a project, yea?
Thanks! Yes I was always on workers free, I think I played with the CPU limit few months ago and it didn't really have any impact. I see now that I don't have the right to change the CPU Limit anymore.
Hey Jack, sorry for the issue! Just to confirm, you cannot see the CPU limit in the dash right?
Hi, hi Jack, it's Ale from Support here at Cloudflare. I've opened a ticket to keep track of it and we are currently reviewing it with Engineering
Yes I could see it before but now I only see the field without a possibility to change the value:
CPU limit.
Set a maximum CPU limit per-invocation.
thanks!
Thanks for the report, the team is working on a fix now 🙂
I believe it's been sent in your ticket already but just for clarity here, the fix was released