You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
|`delaySeconds` (when sending or retrying) | 12 hours |
28
+
| Requests to the Queues API (incl. pulls/acks) |[1200 requests / 5 mins](/fundamentals/api/reference/limits/)|
29
29
30
30
31
31
@@ -40,3 +40,24 @@ import { Render } from "~/components"
40
40
<sup>5</sup> Refer to [Workers limits](/workers/platform/limits/#cpu-time).
41
41
42
42
<Renderfile="limits_increase"product="workers" />
43
+
44
+
### Increasing Queue Consumer CPU limits
45
+
Queue consumers are Worker scripts, and share the same [per invocation CPU limits](/workers/platform/limits/#worker-limits) as any Workers do. Note that CPU time is active processing time: not time spent waiting on network requests, storage calls, or other general I/O, which don't count towards your CPU time or Workflows compute consumption.
46
+
47
+
By default, the maximum CPU time per Workflow invocation is set to 30 seconds, but can be increased for all invocations associated with a Queue consumer by setting `limits.cpu_ms` in your Wrangler configuration:
0 commit comments