Skip to content
Back to the playbook

Fixing Workers CPU time limit exceeded (Error 1102)

Cloudflare WorkersWranglerrevision 1

Diagnostic tree

  1. In progressWorker times out only in productionThe Worker fails with Error 1102 in production while the same code path never times out locally under `wrangler dev`. CPU time (active execution) is capped by the platform; wrangler dev does not enforce that same cap, which is exactly why this only reproduces once deployed.
View the whole map (7 more steps)
  • Confirm it's CPU time, not a request timeout
  • Profile the hot path and/or raise the CPU limit
  • Check whether it's actually a slow await, not CPU work
  • This is a latency problem, not a CPU-time problem
  • Not resolved — escalate
  • Re-run the same production request path
  • Resolved

What to test

Worker times out only in production

The Worker fails with Error 1102 in production while the same code path never times out locally under `wrangler dev`. CPU time (active execution) is capped by the platform; wrangler dev does not enforce that same cap, which is exactly why this only reproduces once deployed.

What happened?

Passed