Workers Paid Plan Upgrade Not Applying – Still Hitting 10ms CPU Limit
WorkersHi, I'm running into a frustrating issue after upgrading to the Workers Paid plan: my Worker is still being terminated with "Worker exceeded CPU time limit" errors around 10-15ms of CPU time (e.g., logs show ~14ms but it fails), and I've explicitly set higher.
Details:
- Account is on Workers Paid (dashboard confirms Paid subscription is active)
- wrangler.jsonc includes:
- Multiple wrangler deploy runs (fresh redeploys)
- Worker type: standard Worker
- Dashboard / logs show CPU time around 14ms
I've seen similar reports in this channel (exact same symptoms: upgraded but still 10ms enforcement, "limits imposed as if still on free plan").
Could someone from the team check if my account/Worker is correctly flagged as Paid with the higher CPU limit?
Happy to provide:
Worker name: mugenzo
Details:
- Account is on Workers Paid (dashboard confirms Paid subscription is active)
- wrangler.jsonc includes:
cpu_ms: 30000- Multiple wrangler deploy runs (fresh redeploys)
- Worker type: standard Worker
- Dashboard / logs show CPU time around 14ms
I've seen similar reports in this channel (exact same symptoms: upgraded but still 10ms enforcement, "limits imposed as if still on free plan").
Could someone from the team check if my account/Worker is correctly flagged as Paid with the higher CPU limit?
Happy to provide:
Worker name: mugenzo
Welcome to the official Cloudflare Developers server. Here you can ask for help and stay updated with the latest news
86,942Members
Resources
Similar Threads
Was this page helpful?
