配額會指定您可使用的可計數共用資源數量。配額是由 Cloud Tasks 等 Google Cloud 服務定義。
系統限制是固定值，無法變更。
Google Cloud 會使用配額來確保公平性，並減少資源使用量和可用性突然暴增的情況。配額會限制專案可使用的Google Cloud 資源 Google Cloud 數量。配額適用於各種資源類型，包括硬體、軟體和網路元件。舉例來說，配額可以限制對服務發出的 API 呼叫數、專案並行使用的負載平衡器數量，或是可建立的專案數量。配額可以預防服務過載，進而保障Google Cloud 使用者社群的權益。配額也能協助您管理自己的 Google Cloud 資源。
如果沒有任何 API 對佇列進行方法呼叫，且該佇列在此期間內沒有分派任何工作，則佇列將變為 INACTIVE。
工作保留時間上限
31 天
工作從加入佇列至遭到系統自動刪除之間的時間長度。
工作排程時間上限
從當前日期與時間起 30 天內
未來可排程工作的時間長度上限。
重新建立佇列的等待時間
7 天
刪除佇列後，您必須等到這段時間過去才能重新建立名稱相同的佇列。
增加配額
如要增加配額，請前往 Google Cloud 主控台的「配額」頁面並選取「編輯配額」來調整，但不得超過相應的配額上限。如要提高原有的配額上限，只要在編輯配額時指定想要提高的配額量，並說明需要提高配額的理由，然後提交新的配額設定即可。我們會在收到您的要求後通知您，並有可能與您聯絡，以進一步詢問相關細節。審核完成後，我們會告知您要求是否獲得核准。
[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間：2025-09-10 (世界標準時間)。"],[],[],null,["This document lists the quotas and system limits that apply to\nCloud Tasks.\n\n- *Quotas* specify the amount of a countable, shared resource that you can use. Quotas are defined by Google Cloud services such as Cloud Tasks.\n- *System limits* are fixed values that cannot be changed.\n\nQuotas\n\nGoogle Cloud uses quotas to help ensure fairness and reduce\nspikes in resource use and availability. A quota restricts how much of a\nGoogle Cloud resource your Google Cloud project can use. Quotas\napply to a range of resource types, including hardware, software, and network\ncomponents. For example, quotas can restrict the number of API calls to a\nservice, the number of load balancers used concurrently by your project, or the\nnumber of projects that you can create. Quotas protect the community of\nGoogle Cloud users by preventing the overloading of services. Quotas also\nhelp you to manage your own Google Cloud resources.\n\nThe Cloud Quotas system does the following:\n\n- Monitors your consumption of Google Cloud products and services\n- Restricts your consumption of those resources\n- Provides a way to [request changes to the quota value](/docs/quotas/help/request_increase) and [automate quota adjustments](/docs/quotas/quota-adjuster)\n\nIn most cases, when you attempt to consume more of a resource than its quota\nallows, the system blocks access to the resource, and the task that\nyou're trying to perform fails.\n\nQuotas generally apply at the Google Cloud project\nlevel. Your use of a resource in one project doesn't affect\nyour available quota in another project. Within a Google Cloud project, quotas\nare shared across all applications and IP addresses.\n\nThe following table describes the quotas for Cloud Tasks resources.\n\n| Resource | Console quota name | Default value | Description |\n|--------------------------|-----------------------------------------------|----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Maximum number of queues | **Number of queues per region** | 1,000 per region | The total number of queues (for both HTTP and App Engine targets) that can exist in a project per region, including the default queue. Queues that process tasks for App Engine targets must be in the same region as the App Engine app. This is the quota for queues created using Cloud Tasks API methods. Any queues created using `queue.yaml`, however, are based on the older Task Queues method. These queues continue to have an initial quota of 100. |\n| API requests | **Requests per minute per region** | 6,000,000 per minute | The total number of API requests that can be made per minute. |\n| Force run task requests | **Run task requests per minute per region** | 60 per minute | The total number of [`run task`](/tasks/docs/reference/rest/v2/projects.locations.queues.tasks/run) requests per minute. This API is intended for manual debugging and is unrelated to normal task execution. |\n| List requests | **List group requests per minute per region** | 600 per minute | The total number of [`list tasks`](/tasks/docs/reference/rest/v2/projects.locations.queues.tasks/list), [`list queues`](/tasks/docs/reference/rest/v2/projects.locations.queues/list), and [`list locations`](/tasks/docs/reference/rest/v2/projects.locations/list) requests per minute. |\n\nTo adjust most quotas, use the Google Cloud console.\nFor more information, see\n[Request a quota adjustment](/docs/quotas/help/request_increase).\n\nSystem limits\n\n\nThere are also *system limits* on Cloud Tasks resources.\nSystem limits can't be changed.\n\nThe following table describes the system limits for Cloud Tasks.\n\n| Resource | Value | Description |\n|----------------------------------|------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Queue dispatch rate | 500 tasks per second per queue | The maximum rate at which tasks can be dispatched from a queue. To dispatch at higher rates, use multiple queues. |\n| Maximum task size | 1 MB | The maximum size of a task that can be added to a queue. |\n| Task deduplication window | Up to 24 hours | The time period during which adding a task with the same name as a recently deleted task will cause the service to reject it with an error. This is the length of time that task deduplication remains in effect after a task is deleted. |\n| Inactive queues | Inactive after 30 days | A queue is considered `INACTIVE` if no method calls are made to it from any API, and it has had no task dispatches for this period. |\n| Maximum task retention | 31 days | The time between when a task is added to a queue and when it is automatically deleted. |\n| Maximum schedule time for a task | 30 days from current date and time | The maximum amount of time in the future that a task can be scheduled. |\n| Queue re-creation | 7 days | The time you must wait after deleting a queue to re-create a queue with the same name. |"]]
