App Engine HTTP queue.
The task will be delivered to the App Engine application hostname specified by its [AppEngineHttpQueue][google.cloud.tasks.v2beta3.AppEngineHttpQueue] and [AppEngineHttpRequest][google.cloud.tasks.v2beta3.AppEngineHttpRequest]. The documentation for [AppEngineHttpRequest][google.cloud.tasks.v2beta3.AppEngineHttpRequest] explains how the task's host URL is constructed.
Using [AppEngineHttpQueue][google.cloud.tasks.v2beta3.AppEngineHttpQueue] requires
Google IAM permission for the project
and the following scope:
App Engine HTTP request.
The message defines the HTTP request that is sent to an App Engine app when the task is dispatched.
Using [AppEngineHttpRequest][google.cloud.tasks.v2beta3.AppEngineHttpRequest] requires
Google IAM permission for the project
and the following scope:
The task will be delivered to the App Engine app which belongs to the same project as the queue. For more information, see How Requests are Routed and how routing is affected by dispatch files. Traffic is encrypted during transport and never leaves Google datacenters. Because this traffic is carried over a communication mechanism internal to Google, you cannot explicitly set the protocol (for example, HTTP or HTTPS). The request to the handler, however, will appear to have used the HTTP protocol.
The [AppEngineRouting][google.cloud.tasks.v2beta3.AppEngineRouting] used to construct the URL that the task is delivered to can be set at the queue-level or task-level:
- If set, [app_engine_routing_override][google.cloud.tasks.v2beta3.AppEngineHttpQueue.app_engine_routing_override] is used for all tasks in the queue, no matter what the setting is for the [task-level app_engine_routing][google.cloud.tasks.v2beta3.AppEngineHttpRequest.app_engine_routing].
url that the task will be sent to is:
Tasks can be dispatched to secure app handlers, unsecure app handlers, and
URIs restricted with
Because tasks are not run as any user, they cannot be dispatched to URIs
Task dispatches also do not follow redirects.
The task attempt has succeeded if the app's request handler returns an HTTP
response code in the range [
299]. The task attempt has failed if
the app's handler returns a non-2xx response code or Cloud Tasks does
not receive response before the [deadline][google.cloud.tasks.v2beta3.Task.dispatch_deadline]. Failed
tasks will be retried according to the
503 (Service Unavailable) is
considered an App Engine system error instead of an application error and
will cause Cloud Tasks' traffic congestion control to temporarily throttle
the queue's dispatches. Unlike other types of task targets, a
429 (Too Many
Requests) response from an app handler does not cause traffic congestion
control to throttle the queue.
App Engine Routing.
Defines routing characteristics specific to App Engine - service, version, and instance.
For more information about services, versions, and instances see An Overview of App Engine, Microservices Architecture on Google App Engine, App Engine Standard request routing, and App Engine Flex request routing.
The status of a task attempt.
Cloud Tasks allows developers to manage the execution of background work in their applications.
Base class for server-side implementations of CloudTasks
Client for CloudTasks
CloudTasks client wrapper, for convenient use.
Builder class for CloudTasksClient to provide simple configuration of credentials, endpoint etc.
CloudTasks client wrapper implementation, for convenient use.
Settings for a CloudTasksClient.
Request message for [CreateQueue][google.cloud.tasks.v2beta3.CloudTasks.CreateQueue].
Request message for [CreateTask][google.cloud.tasks.v2beta3.CloudTasks.CreateTask].
Request message for [DeleteQueue][google.cloud.tasks.v2beta3.CloudTasks.DeleteQueue].
Request message for deleting a task using [DeleteTask][google.cloud.tasks.v2beta3.CloudTasks.DeleteTask].
Request message for [GetQueue][google.cloud.tasks.v2beta3.CloudTasks.GetQueue].
Request message for getting a task using [GetTask][google.cloud.tasks.v2beta3.CloudTasks.GetTask].
The task will be pushed to the worker as an HTTP request. If the worker
or the redirected worker acknowledges the task by returning a successful HTTP
response code ([
299]), the task will removed from the queue. If
any other HTTP response code is returned or no response is received, the
task will be retried according to the following:
User-specified throttling: [retry configuration][Queue.RetryConfig], [rate limits][Queue.RateLimits], and the [queue's state][google.cloud.tasks.v2beta3.Queue.state].
System throttling: To prevent the worker from overloading, Cloud Tasks may temporarily reduce the queue's effective rate. User-specified settings will not be changed.
System throttling happens because:
Cloud Tasks backoffs on all errors. Normally the backoff specified in [rate limits][Queue.RateLimits] will be used. But if the worker returns
429(Too Many Requests),
503(Service Unavailable), or the rate of errors is high, Cloud Tasks will use a higher backoff rate. The retry specified in the
Retry-AfterHTTP response header is considered.
To prevent traffic spikes and to smooth sudden large traffic spikes, dispatches ramp up slowly when the queue is newly created or idle and if large numbers of tasks suddenly become available to dispatch (due to spikes in create task rates, the queue being unpaused, or many tasks that are scheduled at the same time).
Request message for [ListQueues][google.cloud.tasks.v2beta3.CloudTasks.ListQueues].
Response message for [ListQueues][google.cloud.tasks.v2beta3.CloudTasks.ListQueues].
Request message for listing tasks using [ListTasks][google.cloud.tasks.v2beta3.CloudTasks.ListTasks].
Response message for listing tasks using [ListTasks][google.cloud.tasks.v2beta3.CloudTasks.ListTasks].
Resource name for the 'location' resource.
Contains information needed for generating an OAuth token. This type of authorization should generally only be used when calling Google APIs hosted on *.googleapis.com.
Contains information needed for generating an OpenID Connect token. This type of authorization can be used for many scenarios, including calling Cloud Run, or endpoints where you intend to validate the token yourself.
Request message for [PauseQueue][google.cloud.tasks.v2beta3.CloudTasks.PauseQueue].
Request message for [PurgeQueue][google.cloud.tasks.v2beta3.CloudTasks.PurgeQueue].
A queue is a container of related tasks. Queues are configured to manage how those tasks are dispatched. Configurable properties include rate limits, retry options, queue types, and others.
Container for nested types declared in the Queue message type.
Resource name for the 'queue' resource.
This message determines the maximum rate that tasks can be dispatched by a queue, regardless of whether the dispatch is a first task attempt or a retry.
Note: The debugging command, [RunTask][google.cloud.tasks.v2beta3.CloudTasks.RunTask], will run a task even if the queue has reached its [RateLimits][google.cloud.tasks.v2beta3.RateLimits].
Request message for [ResumeQueue][google.cloud.tasks.v2beta3.CloudTasks.ResumeQueue].
These settings determine when a failed task attempt is retried.
Request message for forcing a task to run now using [RunTask][google.cloud.tasks.v2beta3.CloudTasks.RunTask].
Configuration options for writing logs to Stackdriver Logging.
A unit of scheduled work.
Container for nested types declared in the Task message type.
Resource name for the 'task' resource.
Request message for [UpdateQueue][google.cloud.tasks.v2beta3.CloudTasks.UpdateQueue].
The HTTP method used to execute the task.
Enum of possible cases for the "authorization_header" oneof.
Enum of possible cases for the "queue_type" oneof.
State of the queue.
Enum of possible cases for the "payload_type" oneof.
The view specifies a subset of [Task][google.cloud.tasks.v2beta3.Task] data.
When a task is returned in a response, not all information is retrieved by default because some data, such as payloads, might be desirable to return only when needed because of its large size or because of the sensitivity of data that it contains.