This message has oneof_ fields (mutually exclusive fields).
For each oneof, at most one member field can be set at the same time.
Setting any member of the oneof automatically clears all other
Optionally caller-specified in
The task name.
The task name must have the following format:
- PROJECT_ID can contain letters ([A-Za-z]), numbers
([0-9]), hyphens (-), colons (:), or periods (.). For
more information, see `Identifying
The time when the task is scheduled to be attempted or
schedule_time will be truncated to the nearest
Output only. The time that the task was created.
create_time will be truncated to the nearest second.
The deadline for requests sent to the worker. If the worker
does not respond by this deadline then the request is
cancelled and the attempt is marked as a
DEADLINE_EXCEEDED failure. Cloud Tasks will retry the
task according to the
Note that when the request is cancelled, Cloud Tasks will
stop listing for the response, but whether the worker stops
processing depends on the worker. For example, if the worker
is stuck, it may not react to cancelled requests.
The default and maximum values depend on the type of
- For HTTP tasks, the
default is 10 minutes. The deadline must be in the
interval [15 seconds, 30 minutes].
- For [App Engine
indicates that the request has the default deadline. The
default deadline depends on the `scaling
Output only. The number of attempts
This count includes attempts which have been
dispatched but haven't received a response.
Output only. The number of attempts which
have received a response.
Output only. The status of the task's first attempt.
will be set. The other
Attempt information is not
retained by Cloud Tasks.
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.