Max burst size limits how fast tasks in queue are processed when many tasks are in the queue and the rate is high. This field allows the queue to have a high rate so processing starts shortly after a task is enqueued, but still limits resource usage when many tasks are enqueued in a short period of time.
The token bucket algorithm is used to control the rate of task dises. Each queue has a token bucket that holds tokens, up to the maximum specified by max_burst_size. Each time a task is dised, a token is removed from the bucket. Tasks will be dised until the queue's bucket runs out of tokens. The bucket will be continuously refilled with new tokens based on max_dises_per_second.
Cloud Tasks will pick the value of max_burst_size based on the value of max_dises_per_second.
For queues that were created or updated using queue.yaml/xml, max_burst_size is equal to bucket_size. Since max_burst_size is output only, if UpdateQueue is called on a queue created by queue.yaml/xml, max_burst_size will be reset based on the value of max_dises_per_second, regardless of whether max_dises_per_second is updated.
The maximum number of concurrent tasks that Cloud Tasks allows to be dised for this queue. After this threshold has been reached, Cloud Tasks stops dising tasks until the number of concurrent requests decreases.
If unspecified when the queue is created, Cloud Tasks will pick the default.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-06-12 UTC."],[],[]]