Stay organized with collections
Save and categorize content based on your preferences.
Resume a queue. This method resumes a queue after it has been PAUSED or
DISABLED. The state of a queue is stored in the queue's state; after
calling this method it will be set to RUNNING. WARNING: Resuming many
high-QPS queues at the same time can lead to target overloading. If you
are resuming high-QPS queues, follow the 500/50/5 pattern described in
Managing Cloud Tasks Scaling
Risks.
Arguments
Parameters
name
string
Required. The queue name. For example: projects/PROJECT_ID/location/LOCATION_ID/queues/QUEUE_ID
Raised exceptions
Exceptions
ConnectionError
In case of a network problem (such as DNS failure or refused connection).
HttpError
If the response status is >= 400 (excluding 429 and 503).
TimeoutError
If a long-running operation takes longer to finish than the specified timeout limit.
TypeError
If an operation or function receives an argument of the wrong type.
ValueError
If an operation or function receives an argument of the right type but an inappropriate value. For example, a negative timeout.
Response
If successful, the response contains an instance of Queue.
Subworkflow snippet
Some fields might be optional or required.
To identify required fields, refer to the API documentation.
[[["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-08-29 UTC."],[],[],null,["# Method: googleapis.cloudtasks.v2.projects.locations.queues.resume\n\nResume a queue. This method resumes a queue after it has been PAUSED or\nDISABLED. The state of a queue is stored in the queue's state; after\ncalling this method it will be set to RUNNING. WARNING: Resuming many\nhigh-QPS queues at the same time can lead to target overloading. If you\nare resuming high-QPS queues, follow the 500/50/5 pattern described in\n[Managing Cloud Tasks Scaling\nRisks](https://cloud.google.com/tasks/docs/manage-cloud-task-scaling).\n\nArguments\n---------\n\nRaised exceptions\n-----------------\n\nResponse\n--------\n\nIf successful, the response contains an instance of [`Queue`](/workflows/docs/reference/googleapis/cloudtasks/v2/Overview#Queue).\n\nSubworkflow snippet\n-------------------\n\nSome fields might be optional or required.\nTo identify required fields, refer to the [API documentation](https://cloud.google.com/tasks/docs/reference/rest/v2/projects.locations.queues/resume). \n\n### YAML\n\n```yaml\n- resume:\n call: googleapis.cloudtasks.v2.projects.locations.queues.resume\n args:\n name: ...\n result: resumeResult\n```\n\n### JSON\n\n```json\n[\n {\n \"resume\": {\n \"call\": \"googleapis.cloudtasks.v2.projects.locations.queues.resume\",\n \"args\": {\n \"name\": \"...\"\n },\n \"result\": \"resumeResult\"\n }\n }\n]\n```"]]