#Workers Paid active but CPU still capped around 10–20ms

5 messages · Page 1 of 1 (latest)

pearl hare
#

Hi, my account has an active Workers Paid subscription, but my Worker still behaves like it is capped at around 10–20ms CPU time.

What I already checked:

  • Workers Paid subscription is active
  • CPU limit was set higher in dashboard
  • Redeployed multiple times
  • Still getting exceededCpu / behavior similar to free or legacy limits

Could someone please verify whether:

  1. this Worker is still on legacy Bundled,
  2. the account/worker was not fully migrated to Standard,
    or
  3. the higher CPU limit was not actually applied server-side?
#

Worker name: patternaly

I have already linked my Cloudflare account to Discord. If needed, I can also share screenshots showing:

  • Workers Paid is active
  • CPU limit is set higher
  • requests still fail around 10–20ms
warped cedar
#

I hope the above guide helps.

pearl hare
# warped cedar Hey there, sorry for the issues. You can read more about it here: https://develo...

I have already read that page. My concern is exactly that the documented limits do not match my actual behavior.

According to the docs, Workers Paid should have a default CPU limit of 30 seconds, and legacy Bundled Workers are capped at 50 ms. My Worker is still failing around 10–20 ms.

Could someone please verify whether:

  1. this Worker is still on legacy Bundled,
  2. it was not fully migrated to Standard,
    or
  3. the higher CPU limit was not actually applied server-side?