Resume
Resume stopped or failed transfer.
Authorizations
The Authorization header expects a Bearer token.
Body
Response
A successful response.
Creation timestamp.
ID of the user or service account who initiated the operation.
Human-readable description of the operation. 0-256 characters long.
The time when the operation has finished.
ID of the operation.
Any contains an arbitrary serialized protocol buffer message along with a
URL that describes the type of the serialized message
Information for tracking the progress of a task (e.g., an API operation or background maintenance action). This serves as a UI contract and may be directly reflected in CLI, Console, and other tools.
Any contains an arbitrary serialized protocol buffer message along with a
URL that describes the type of the serialized message
ID of the resource that this operation creates, updates, deletes or otherwise changes.
If the operation affects multiple resources or does not affect any API resources at all (e.g. a routine maintenance operation visible to the user), the [resource_id] must be empty.
The Status type defines a logical error model that is suitable for
different programming environments, including REST APIs and RPC APIs. It is
used by gRPC. Each Status message contains
three pieces of data: error code, error message, and error details.
You can find out more about this error model and how to work with it in the API Design Guide.