Lines Matching full:tasks
75 …Tasks API</a> . <a href="cloudtasks_v2beta3.projects.html">projects</a> . <a href="cloudtasks_v2be…
88 <p class="firstline">Lists the tasks in a queue.</p>
100 Tasks cannot be updated after creation; there is no UpdateTask command.
125 # `cloudtasks.tasks.fullView` [Google IAM](https://cloud.google.com/iam/)
132 # `projects/PROJECT_ID/locations/LOCATION_ID/queues/QUEUE_ID/tasks/TASK_ID`.
139 # past then Cloud Tasks will set it to the current time.
147 # If the task's queue was created using Cloud Tasks, then another task with
160 # uniform distribution of task ids to store and serve tasks
175 # * System throttling: To prevent the worker from overloading, Cloud Tasks may
181 # * Cloud Tasks backoffs on all errors. Normally the backoff specified in
184 # errors is high, Cloud Tasks will use a higher backoff rate. The retry
189 # if large numbers of tasks suddenly become available to dispatch (due to
190 # spikes in create task rates, the queue being unpaused, or many tasks
201 # are: `http://acme.com` and `https://acme.com/sales:8080`. Cloud Tasks will
258 # * Host: This will be computed by Cloud Tasks and derived from
260 # * Content-Length: This will be computed by Cloud Tasks.
261 # * User-Agent: This will be set to `"Google-Cloud-Tasks"`.
265 # `Content-Type` won't be set by Cloud Tasks. You can explicitly set
310 # is used for all tasks in the queue, no matter what the setting
320 # Tasks can be dispatched to secure app handlers, unsecure app handlers, and
324 # Because tasks are not run as any user, they cannot be dispatched to URIs
332 # the app's handler returns a non-2xx response code or Cloud Tasks does
334 # tasks will be retried according to the
337 # will cause Cloud Tasks' traffic congestion control to temporarily throttle
352 # Cloud Tasks sets some headers to default values:
356 # This header can be modified, but Cloud Tasks will append
361 # Tasks sets the following headers:
368 # * `Content-Length`: This is computed by Cloud Tasks. This value is
377 # In addition, Cloud Tasks sets some headers when the task is dispatched,
382 # visible when the task is returned in a Cloud Tasks response.
393 # is used for all tasks in the queue, no matter what the setting is for the
426 # and instance. Tasks which were created using
437 # For some queues or tasks which were created using the App Engine
441 # instance. For example, some tasks
443 # name; custom domains are not parsed by Cloud Tasks. If
453 # For some queues or tasks which were created using the App Engine
457 # instance. For example, some tasks
459 # name; custom domains are not parsed by Cloud Tasks. If
488 # `projects/PROJECT_ID/locations/LOCATION_ID/queues/QUEUE_ID/tasks/TASK_ID`
544 # is marked as a `DEADLINE_EXCEEDED` failure. Cloud Tasks will retry the
547 # Note that when the request is cancelled, Cloud Tasks will stop listing for
554 # * For HTTP tasks, the default is 10 minutes. The deadline
557 # * For App Engine tasks, 0 indicates that the
569 # [Timeouts](https://cloud.google.com/tasks/docs/creating-appengine-handlers#timeouts).
584 # The other Attempt information is not retained by Cloud Tasks.
641 # * System throttling: To prevent the worker from overloading, Cloud Tasks may
647 # * Cloud Tasks backoffs on all errors. Normally the backoff specified in
650 # errors is high, Cloud Tasks will use a higher backoff rate. The retry
655 # if large numbers of tasks suddenly become available to dispatch (due to
656 # spikes in create task rates, the queue being unpaused, or many tasks
667 # are: `http://acme.com` and `https://acme.com/sales:8080`. Cloud Tasks will
724 # * Host: This will be computed by Cloud Tasks and derived from
726 # * Content-Length: This will be computed by Cloud Tasks.
727 # * User-Agent: This will be set to `"Google-Cloud-Tasks"`.
731 # `Content-Type` won't be set by Cloud Tasks. You can explicitly set
776 # is used for all tasks in the queue, no matter what the setting
786 # Tasks can be dispatched to secure app handlers, unsecure app handlers, and
790 # Because tasks are not run as any user, they cannot be dispatched to URIs
798 # the app's handler returns a non-2xx response code or Cloud Tasks does
800 # tasks will be retried according to the
803 # will cause Cloud Tasks' traffic congestion control to temporarily throttle
818 # Cloud Tasks sets some headers to default values:
822 # This header can be modified, but Cloud Tasks will append
827 # Tasks sets the following headers:
834 # * `Content-Length`: This is computed by Cloud Tasks. This value is
843 # In addition, Cloud Tasks sets some headers when the task is dispatched,
848 # visible when the task is returned in a Cloud Tasks response.
859 # is used for all tasks in the queue, no matter what the setting is for the
892 # and instance. Tasks which were created using
903 # For some queues or tasks which were created using the App Engine
907 # instance. For example, some tasks
909 # name; custom domains are not parsed by Cloud Tasks. If
919 # For some queues or tasks which were created using the App Engine
923 # instance. For example, some tasks
925 # name; custom domains are not parsed by Cloud Tasks. If
954 # `projects/PROJECT_ID/locations/LOCATION_ID/queues/QUEUE_ID/tasks/TASK_ID`
1010 # is marked as a `DEADLINE_EXCEEDED` failure. Cloud Tasks will retry the
1013 # Note that when the request is cancelled, Cloud Tasks will stop listing for
1020 # * For HTTP tasks, the default is 10 minutes. The deadline
1023 # * For App Engine tasks, 0 indicates that the
1035 # [Timeouts](https://cloud.google.com/tasks/docs/creating-appengine-handlers#timeouts).
1050 # The other Attempt information is not retained by Cloud Tasks.
1097 `projects/PROJECT_ID/locations/LOCATION_ID/queues/QUEUE_ID/tasks/TASK_ID` (required)
1126 `projects/PROJECT_ID/locations/LOCATION_ID/queues/QUEUE_ID/tasks/TASK_ID` (required)
1137 `cloudtasks.tasks.fullView` [Google IAM](https://cloud.google.com/iam/)
1161 # * System throttling: To prevent the worker from overloading, Cloud Tasks may
1167 # * Cloud Tasks backoffs on all errors. Normally the backoff specified in
1170 # errors is high, Cloud Tasks will use a higher backoff rate. The retry
1175 # if large numbers of tasks suddenly become available to dispatch (due to
1176 # spikes in create task rates, the queue being unpaused, or many tasks
1187 # are: `http://acme.com` and `https://acme.com/sales:8080`. Cloud Tasks will
1244 # * Host: This will be computed by Cloud Tasks and derived from
1246 # * Content-Length: This will be computed by Cloud Tasks.
1247 # * User-Agent: This will be set to `"Google-Cloud-Tasks"`.
1251 # `Content-Type` won't be set by Cloud Tasks. You can explicitly set
1296 # is used for all tasks in the queue, no matter what the setting
1306 # Tasks can be dispatched to secure app handlers, unsecure app handlers, and
1310 # Because tasks are not run as any user, they cannot be dispatched to URIs
1318 # the app's handler returns a non-2xx response code or Cloud Tasks does
1320 # tasks will be retried according to the
1323 # will cause Cloud Tasks' traffic congestion control to temporarily throttle
1338 # Cloud Tasks sets some headers to default values:
1342 # This header can be modified, but Cloud Tasks will append
1347 # Tasks sets the following headers:
1354 # * `Content-Length`: This is computed by Cloud Tasks. This value is
1363 # In addition, Cloud Tasks sets some headers when the task is dispatched,
1368 # visible when the task is returned in a Cloud Tasks response.
1379 # is used for all tasks in the queue, no matter what the setting is for the
1412 # and instance. Tasks which were created using
1423 # For some queues or tasks which were created using the App Engine
1427 # instance. For example, some tasks
1429 # name; custom domains are not parsed by Cloud Tasks. If
1439 # For some queues or tasks which were created using the App Engine
1443 # instance. For example, some tasks
1445 # name; custom domains are not parsed by Cloud Tasks. If
1474 # `projects/PROJECT_ID/locations/LOCATION_ID/queues/QUEUE_ID/tasks/TASK_ID`
1530 # is marked as a `DEADLINE_EXCEEDED` failure. Cloud Tasks will retry the
1533 # Note that when the request is cancelled, Cloud Tasks will stop listing for
1540 # * For HTTP tasks, the default is 10 minutes. The deadline
1543 # * For App Engine tasks, 0 indicates that the
1555 # [Timeouts](https://cloud.google.com/tasks/docs/creating-appengine-handlers#timeouts).
1570 # The other Attempt information is not retained by Cloud Tasks.
1607 <pre>Lists the tasks in a queue.
1614 The tasks may be returned in any order. The ordering may change at any
1632 `cloudtasks.tasks.fullView` [Google IAM](https://cloud.google.com/iam/)
1636 Fewer tasks than requested might be returned, even if more tasks exist; use
1638 determine if more tasks exist.
1659 { # Response message for listing tasks using ListTasks.
1667 "tasks": [ # The list of tasks.
1682 # * System throttling: To prevent the worker from overloading, Cloud Tasks may
1688 # * Cloud Tasks backoffs on all errors. Normally the backoff specified in
1691 # errors is high, Cloud Tasks will use a higher backoff rate. The retry
1696 # if large numbers of tasks suddenly become available to dispatch (due to
1697 # spikes in create task rates, the queue being unpaused, or many tasks
1708 # are: `http://acme.com` and `https://acme.com/sales:8080`. Cloud Tasks will
1765 # * Host: This will be computed by Cloud Tasks and derived from
1767 # * Content-Length: This will be computed by Cloud Tasks.
1768 # * User-Agent: This will be set to `"Google-Cloud-Tasks"`.
1772 # `Content-Type` won't be set by Cloud Tasks. You can explicitly set
1817 # is used for all tasks in the queue, no matter what the setting
1827 # Tasks can be dispatched to secure app handlers, unsecure app handlers, and
1831 # Because tasks are not run as any user, they cannot be dispatched to URIs
1839 # the app's handler returns a non-2xx response code or Cloud Tasks does
1841 # tasks will be retried according to the
1844 # will cause Cloud Tasks' traffic congestion control to temporarily throttle
1859 # Cloud Tasks sets some headers to default values:
1863 # This header can be modified, but Cloud Tasks will append
1868 # Tasks sets the following headers:
1875 # * `Content-Length`: This is computed by Cloud Tasks. This value is
1884 # In addition, Cloud Tasks sets some headers when the task is dispatched,
1889 # visible when the task is returned in a Cloud Tasks response.
1900 # is used for all tasks in the queue, no matter what the setting is for the
1933 # and instance. Tasks which were created using
1944 # For some queues or tasks which were created using the App Engine
1948 # instance. For example, some tasks
1950 # name; custom domains are not parsed by Cloud Tasks. If
1960 # For some queues or tasks which were created using the App Engine
1964 # instance. For example, some tasks
1966 # name; custom domains are not parsed by Cloud Tasks. If
1995 # `projects/PROJECT_ID/locations/LOCATION_ID/queues/QUEUE_ID/tasks/TASK_ID`
2051 # is marked as a `DEADLINE_EXCEEDED` failure. Cloud Tasks will retry the
2054 # Note that when the request is cancelled, Cloud Tasks will stop listing for
2061 # * For HTTP tasks, the default is 10 minutes. The deadline
2064 # * For App Engine tasks, 0 indicates that the
2076 … # [Timeouts](https://cloud.google.com/tasks/docs/creating-appengine-handlers#timeouts).
2091 # The other Attempt information is not retained by Cloud Tasks.
2146 When this method is called, Cloud Tasks will dispatch the task, even if
2159 If Cloud Tasks receives a successful response from the task's
2173 `projects/PROJECT_ID/locations/LOCATION_ID/queues/QUEUE_ID/tasks/TASK_ID` (required)
2189 # `cloudtasks.tasks.fullView` [Google IAM](https://cloud.google.com/iam/)
2215 # * System throttling: To prevent the worker from overloading, Cloud Tasks may
2221 # * Cloud Tasks backoffs on all errors. Normally the backoff specified in
2224 # errors is high, Cloud Tasks will use a higher backoff rate. The retry
2229 # if large numbers of tasks suddenly become available to dispatch (due to
2230 # spikes in create task rates, the queue being unpaused, or many tasks
2241 # are: `http://acme.com` and `https://acme.com/sales:8080`. Cloud Tasks will
2298 # * Host: This will be computed by Cloud Tasks and derived from
2300 # * Content-Length: This will be computed by Cloud Tasks.
2301 # * User-Agent: This will be set to `"Google-Cloud-Tasks"`.
2305 # `Content-Type` won't be set by Cloud Tasks. You can explicitly set
2350 # is used for all tasks in the queue, no matter what the setting
2360 # Tasks can be dispatched to secure app handlers, unsecure app handlers, and
2364 # Because tasks are not run as any user, they cannot be dispatched to URIs
2372 # the app's handler returns a non-2xx response code or Cloud Tasks does
2374 # tasks will be retried according to the
2377 # will cause Cloud Tasks' traffic congestion control to temporarily throttle
2392 # Cloud Tasks sets some headers to default values:
2396 # This header can be modified, but Cloud Tasks will append
2401 # Tasks sets the following headers:
2408 # * `Content-Length`: This is computed by Cloud Tasks. This value is
2417 # In addition, Cloud Tasks sets some headers when the task is dispatched,
2422 # visible when the task is returned in a Cloud Tasks response.
2433 # is used for all tasks in the queue, no matter what the setting is for the
2466 # and instance. Tasks which were created using
2477 # For some queues or tasks which were created using the App Engine
2481 # instance. For example, some tasks
2483 # name; custom domains are not parsed by Cloud Tasks. If
2493 # For some queues or tasks which were created using the App Engine
2497 # instance. For example, some tasks
2499 # name; custom domains are not parsed by Cloud Tasks. If
2528 # `projects/PROJECT_ID/locations/LOCATION_ID/queues/QUEUE_ID/tasks/TASK_ID`
2584 # is marked as a `DEADLINE_EXCEEDED` failure. Cloud Tasks will retry the
2587 # Note that when the request is cancelled, Cloud Tasks will stop listing for
2594 # * For HTTP tasks, the default is 10 minutes. The deadline
2597 # * For App Engine tasks, 0 indicates that the
2609 # [Timeouts](https://cloud.google.com/tasks/docs/creating-appengine-handlers#timeouts).
2624 # The other Attempt information is not retained by Cloud Tasks.