@@ -175,7 +175,47 @@ class Queue(proto.Message):
175
175
"""
176
176
177
177
class State (proto .Enum ):
178
- r"""State of the queue."""
178
+ r"""State of the queue.
179
+
180
+ Values:
181
+ STATE_UNSPECIFIED (0):
182
+ Unspecified state.
183
+ RUNNING (1):
184
+ The queue is running. Tasks can be dispatched.
185
+
186
+ If the queue was created using Cloud Tasks and the queue has
187
+ had no activity (method calls or task dispatches) for 30
188
+ days, the queue may take a few minutes to re-activate. Some
189
+ method calls may return
190
+ [NOT_FOUND][google.rpc.Code.NOT_FOUND] and tasks may not be
191
+ dispatched for a few minutes until the queue has been
192
+ re-activated.
193
+ PAUSED (2):
194
+ Tasks are paused by the user. If the queue is paused then
195
+ Cloud Tasks will stop delivering tasks from it, but more
196
+ tasks can still be added to it by the user. When a pull
197
+ queue is paused, all
198
+ [LeaseTasks][google.cloud.tasks.v2beta2.CloudTasks.LeaseTasks]
199
+ calls will return a
200
+ [FAILED_PRECONDITION][google.rpc.Code.FAILED_PRECONDITION].
201
+ DISABLED (3):
202
+ The queue is disabled.
203
+
204
+ A queue becomes ``DISABLED`` when
205
+ `queue.yaml <https://cloud.google.com/appengine/docs/python/config/queueref>`__
206
+ or
207
+ `queue.xml <https://cloud.google.com/appengine/docs/standard/java/config/queueref>`__
208
+ is uploaded which does not contain the queue. You cannot
209
+ directly disable a queue.
210
+
211
+ When a queue is disabled, tasks can still be added to a
212
+ queue but the tasks are not dispatched and
213
+ [LeaseTasks][google.cloud.tasks.v2beta2.CloudTasks.LeaseTasks]
214
+ calls return a ``FAILED_PRECONDITION`` error.
215
+
216
+ To permanently delete this queue and all of its tasks, call
217
+ [DeleteQueue][google.cloud.tasks.v2beta2.CloudTasks.DeleteQueue].
218
+ """
179
219
STATE_UNSPECIFIED = 0
180
220
RUNNING = 1
181
221
PAUSED = 2
0 commit comments