Wrangler configuration supports the `subrequests` limit

Introduced 2026-02-03 · score 0.94

HOW TO USE IT

When a Worker invocation needs a request-count cap, set `limits.subrequests` in its Wrangler config. `limits` and `subrequests` are optional; the limit applies at runtime on Cloudflare’s network, not in local development.

{
  "limits": {
    "cpu_ms": 1000,
    "subrequests": 150
  }
}

WHY THIS HELPS

Limit the number of fetch requests a Worker's invocation can make by configuring the Worker limits.

BEFORE THIS CHANGE

Before this change, only `cpu_ms` was supported in Wrangler’s `limits` field.

REQUIREMENTS AND LIMITATIONS

Version: 4.62.0
limits: Configures limits imposed on Worker execution at runtime.
limits.subrequests: Maximum subrequests allowed per invocation.
limits.cpu_ms: Maximum CPU time allowed per invocation, in milliseconds.
Prerequisite: Limits are supported for the Standard Usage Model and are enforced only on Cloudflare’s network, not during local development.
Docs conflict: The current configuration docs say the maximum is 50 for free accounts and 10,000,000 for paid accounts. The release-note example uses 150 without specifying a plan; the current docs’ free-account maximum conflicts with using 150 on a free account. https://developers.cloudflare.com/workers/wrangler/configuration/

FIRST-PARTY EVIDENCE

Check the installed version and the source before using it. Entry JSON

Report a problem with this card

Tools change faster than your agent’s training data.

Changes

Wrangler configuration supports the `subrequests` limit