gcp.cloudscheduler.Job

App Engine HTTP target. If the job providers a App Engine HTTP target the cron will send a request to the service instance Structure is documented below.

The deadline for job attempts. If the request handler does not respond by this deadline then the request is cancelled and the attempt is marked as a DEADLINE_EXCEEDED failure. The failed attempt can be viewed in execution logs. Cloud Scheduler will retry the job according to the RetryConfig. The allowed duration for this deadline is:

• For HTTP targets, between 15 seconds and 30 minutes.
• For App Engine HTTP targets, between 15 seconds and 24 hours.
• Note: For PubSub targets, this field is ignored - setting it will introduce an unresolvable diff. A duration in seconds with up to nine fractional digits, terminated by 's'. Example: "3.5s"

A human-readable description for the job. This string must not contain more than 500 characters.

HTTP target. If the job providers a http_target the cron will send a request to the targeted url Structure is documented below.

The name of the job.

Sets the job to a paused state. Jobs default to being enabled when this property is not set.

The ID of the project in which the resource belongs. If it is not provided, the provider project is used.

Pub/Sub target If the job providers a Pub/Sub target the cron will publish a message to the provided topic Structure is documented below.

Region where the scheduler job resides. If it is not provided, this provider will use the provider default.

By default, if a job does not complete successfully, meaning that an acknowledgement is not received from the handler, then it will be retried with exponential backoff according to the settings Structure is documented below.

Describes the schedule on which the job will be executed.

Specifies the time zone to be used in interpreting schedule. The value of this field must be a time zone name from the tz database.

App Engine HTTP target. If the job providers a App Engine HTTP target the cron will send a request to the service instance Structure is documented below.

The deadline for job attempts. If the request handler does not respond by this deadline then the request is cancelled and the attempt is marked as a DEADLINE_EXCEEDED failure. The failed attempt can be viewed in execution logs. Cloud Scheduler will retry the job according to the RetryConfig. The allowed duration for this deadline is:

• For HTTP targets, between 15 seconds and 30 minutes.
• For App Engine HTTP targets, between 15 seconds and 24 hours.
• Note: For PubSub targets, this field is ignored - setting it will introduce an unresolvable diff. A duration in seconds with up to nine fractional digits, terminated by 's'. Example: "3.5s"

A human-readable description for the job. This string must not contain more than 500 characters.

HTTP target. If the job providers a http_target the cron will send a request to the targeted url Structure is documented below.

The name of the job.

Sets the job to a paused state. Jobs default to being enabled when this property is not set.

The ID of the project in which the resource belongs. If it is not provided, the provider project is used.

Pub/Sub target If the job providers a Pub/Sub target the cron will publish a message to the provided topic Structure is documented below.

Region where the scheduler job resides. If it is not provided, this provider will use the provider default.

By default, if a job does not complete successfully, meaning that an acknowledgement is not received from the handler, then it will be retried with exponential backoff according to the settings Structure is documented below.

Describes the schedule on which the job will be executed.

Specifies the time zone to be used in interpreting schedule. The value of this field must be a time zone name from the tz database.

App Engine HTTP target. If the job providers a App Engine HTTP target the cron will send a request to the service instance Structure is documented below.

The deadline for job attempts. If the request handler does not respond by this deadline then the request is cancelled and the attempt is marked as a DEADLINE_EXCEEDED failure. The failed attempt can be viewed in execution logs. Cloud Scheduler will retry the job according to the RetryConfig. The allowed duration for this deadline is:

• For HTTP targets, between 15 seconds and 30 minutes.
• For App Engine HTTP targets, between 15 seconds and 24 hours.
• Note: For PubSub targets, this field is ignored - setting it will introduce an unresolvable diff. A duration in seconds with up to nine fractional digits, terminated by 's'. Example: "3.5s"

A human-readable description for the job. This string must not contain more than 500 characters.

HTTP target. If the job providers a http_target the cron will send a request to the targeted url Structure is documented below.

The name of the job.

Sets the job to a paused state. Jobs default to being enabled when this property is not set.

The ID of the project in which the resource belongs. If it is not provided, the provider project is used.

Pub/Sub target If the job providers a Pub/Sub target the cron will publish a message to the provided topic Structure is documented below.

Region where the scheduler job resides. If it is not provided, this provider will use the provider default.

By default, if a job does not complete successfully, meaning that an acknowledgement is not received from the handler, then it will be retried with exponential backoff according to the settings Structure is documented below.

Describes the schedule on which the job will be executed.

Specifies the time zone to be used in interpreting schedule. The value of this field must be a time zone name from the tz database.

App Engine HTTP target. If the job providers a App Engine HTTP target the cron will send a request to the service instance Structure is documented below.

The deadline for job attempts. If the request handler does not respond by this deadline then the request is cancelled and the attempt is marked as a DEADLINE_EXCEEDED failure. The failed attempt can be viewed in execution logs. Cloud Scheduler will retry the job according to the RetryConfig. The allowed duration for this deadline is:

• For HTTP targets, between 15 seconds and 30 minutes.
• For App Engine HTTP targets, between 15 seconds and 24 hours.
• Note: For PubSub targets, this field is ignored - setting it will introduce an unresolvable diff. A duration in seconds with up to nine fractional digits, terminated by 's'. Example: "3.5s"

A human-readable description for the job. This string must not contain more than 500 characters.

HTTP target. If the job providers a http_target the cron will send a request to the targeted url Structure is documented below.

The name of the job.

Sets the job to a paused state. Jobs default to being enabled when this property is not set.

The ID of the project in which the resource belongs. If it is not provided, the provider project is used.

Pub/Sub target If the job providers a Pub/Sub target the cron will publish a message to the provided topic Structure is documented below.

Region where the scheduler job resides. If it is not provided, this provider will use the provider default.

By default, if a job does not complete successfully, meaning that an acknowledgement is not received from the handler, then it will be retried with exponential backoff according to the settings Structure is documented below.

Describes the schedule on which the job will be executed.

Specifies the time zone to be used in interpreting schedule. The value of this field must be a time zone name from the tz database.

App Engine HTTP target. If the job providers a App Engine HTTP target the cron will send a request to the service instance Structure is documented below.

The deadline for job attempts. If the request handler does not respond by this deadline then the request is cancelled and the attempt is marked as a DEADLINE_EXCEEDED failure. The failed attempt can be viewed in execution logs. Cloud Scheduler will retry the job according to the RetryConfig. The allowed duration for this deadline is:

• For HTTP targets, between 15 seconds and 30 minutes.
• For App Engine HTTP targets, between 15 seconds and 24 hours.
• Note: For PubSub targets, this field is ignored - setting it will introduce an unresolvable diff. A duration in seconds with up to nine fractional digits, terminated by 's'. Example: "3.5s"

A human-readable description for the job. This string must not contain more than 500 characters.

HTTP target. If the job providers a http_target the cron will send a request to the targeted url Structure is documented below.

The name of the job.

Sets the job to a paused state. Jobs default to being enabled when this property is not set.

The ID of the project in which the resource belongs. If it is not provided, the provider project is used.

Pub/Sub target If the job providers a Pub/Sub target the cron will publish a message to the provided topic Structure is documented below.

Region where the scheduler job resides. If it is not provided, this provider will use the provider default.

By default, if a job does not complete successfully, meaning that an acknowledgement is not received from the handler, then it will be retried with exponential backoff according to the settings Structure is documented below.

Describes the schedule on which the job will be executed.

Specifies the time zone to be used in interpreting schedule. The value of this field must be a time zone name from the tz database.

App Engine HTTP target. If the job providers a App Engine HTTP target the cron will send a request to the service instance Structure is documented below.

The deadline for job attempts. If the request handler does not respond by this deadline then the request is cancelled and the attempt is marked as a DEADLINE_EXCEEDED failure. The failed attempt can be viewed in execution logs. Cloud Scheduler will retry the job according to the RetryConfig. The allowed duration for this deadline is:

• For HTTP targets, between 15 seconds and 30 minutes.
• For App Engine HTTP targets, between 15 seconds and 24 hours.
• Note: For PubSub targets, this field is ignored - setting it will introduce an unresolvable diff. A duration in seconds with up to nine fractional digits, terminated by 's'. Example: "3.5s"

A human-readable description for the job. This string must not contain more than 500 characters.

HTTP target. If the job providers a http_target the cron will send a request to the targeted url Structure is documented below.

The name of the job.

Sets the job to a paused state. Jobs default to being enabled when this property is not set.

The ID of the project in which the resource belongs. If it is not provided, the provider project is used.

Pub/Sub target If the job providers a Pub/Sub target the cron will publish a message to the provided topic Structure is documented below.

Region where the scheduler job resides. If it is not provided, this provider will use the provider default.

By default, if a job does not complete successfully, meaning that an acknowledgement is not received from the handler, then it will be retried with exponential backoff according to the settings Structure is documented below.

Describes the schedule on which the job will be executed.

Specifies the time zone to be used in interpreting schedule. The value of this field must be a time zone name from the tz database.

The provider-assigned unique ID for this managed resource.

State of the job.

The provider-assigned unique ID for this managed resource.

State of the job.

The provider-assigned unique ID for this managed resource.

State of the job.

The provider-assigned unique ID for this managed resource.

State of the job.

The provider-assigned unique ID for this managed resource.

State of the job.

The provider-assigned unique ID for this managed resource.

State of the job.

The relative URI. The relative URL must begin with "/" and must be a valid HTTP relative URL. It can contain a path, query string arguments, and # fragments. If the relative URL is empty, then the root path "/" will be used. No spaces are allowed, and the maximum length allowed is 2083 characters

App Engine Routing setting for the job. Structure is documented below.

HTTP request body. A request body is allowed only if the HTTP method is POST or PUT. It will result in invalid argument error to set a body on a job with an incompatible HttpMethod. A base64-encoded string.

HTTP request headers. This map contains the header field names and values. Headers can be set when the job is created.

Which HTTP method to use for the request.

The relative URI. The relative URL must begin with "/" and must be a valid HTTP relative URL. It can contain a path, query string arguments, and # fragments. If the relative URL is empty, then the root path "/" will be used. No spaces are allowed, and the maximum length allowed is 2083 characters

App Engine Routing setting for the job. Structure is documented below.

HTTP request body. A request body is allowed only if the HTTP method is POST or PUT. It will result in invalid argument error to set a body on a job with an incompatible HttpMethod. A base64-encoded string.

HTTP request headers. This map contains the header field names and values. Headers can be set when the job is created.

Which HTTP method to use for the request.

The relative URI. The relative URL must begin with "/" and must be a valid HTTP relative URL. It can contain a path, query string arguments, and # fragments. If the relative URL is empty, then the root path "/" will be used. No spaces are allowed, and the maximum length allowed is 2083 characters

App Engine Routing setting for the job. Structure is documented below.

HTTP request body. A request body is allowed only if the HTTP method is POST or PUT. It will result in invalid argument error to set a body on a job with an incompatible HttpMethod. A base64-encoded string.

HTTP request headers. This map contains the header field names and values. Headers can be set when the job is created.

Which HTTP method to use for the request.

The relative URI. The relative URL must begin with "/" and must be a valid HTTP relative URL. It can contain a path, query string arguments, and # fragments. If the relative URL is empty, then the root path "/" will be used. No spaces are allowed, and the maximum length allowed is 2083 characters

App Engine Routing setting for the job. Structure is documented below.

HTTP request body. A request body is allowed only if the HTTP method is POST or PUT. It will result in invalid argument error to set a body on a job with an incompatible HttpMethod. A base64-encoded string.

HTTP request headers. This map contains the header field names and values. Headers can be set when the job is created.

Which HTTP method to use for the request.

The relative URI. The relative URL must begin with "/" and must be a valid HTTP relative URL. It can contain a path, query string arguments, and # fragments. If the relative URL is empty, then the root path "/" will be used. No spaces are allowed, and the maximum length allowed is 2083 characters

App Engine Routing setting for the job. Structure is documented below.

HTTP request body. A request body is allowed only if the HTTP method is POST or PUT. It will result in invalid argument error to set a body on a job with an incompatible HttpMethod. A base64-encoded string.

HTTP request headers. This map contains the header field names and values. Headers can be set when the job is created.

Which HTTP method to use for the request.

The relative URI. The relative URL must begin with "/" and must be a valid HTTP relative URL. It can contain a path, query string arguments, and # fragments. If the relative URL is empty, then the root path "/" will be used. No spaces are allowed, and the maximum length allowed is 2083 characters

App Engine Routing setting for the job. Structure is documented below.

HTTP request body. A request body is allowed only if the HTTP method is POST or PUT. It will result in invalid argument error to set a body on a job with an incompatible HttpMethod. A base64-encoded string.

HTTP request headers. This map contains the header field names and values. Headers can be set when the job is created.

Which HTTP method to use for the request.

App instance. By default, the job is sent to an instance which is available when the job is attempted.

App service. By default, the job is sent to the service which is the default service when the job is attempted.

App version. By default, the job is sent to the version which is the default version when the job is attempted.

App instance. By default, the job is sent to an instance which is available when the job is attempted.

App service. By default, the job is sent to the service which is the default service when the job is attempted.

App version. By default, the job is sent to the version which is the default version when the job is attempted.

App instance. By default, the job is sent to an instance which is available when the job is attempted.

App service. By default, the job is sent to the service which is the default service when the job is attempted.

App version. By default, the job is sent to the version which is the default version when the job is attempted.

App instance. By default, the job is sent to an instance which is available when the job is attempted.

App service. By default, the job is sent to the service which is the default service when the job is attempted.

App version. By default, the job is sent to the version which is the default version when the job is attempted.

App instance. By default, the job is sent to an instance which is available when the job is attempted.

App service. By default, the job is sent to the service which is the default service when the job is attempted.

App version. By default, the job is sent to the version which is the default version when the job is attempted.

App instance. By default, the job is sent to an instance which is available when the job is attempted.

App service. By default, the job is sent to the service which is the default service when the job is attempted.

App version. By default, the job is sent to the version which is the default version when the job is attempted.

The full URI path that the request will be sent to.

HTTP request body. A request body is allowed only if the HTTP method is POST, PUT, or PATCH. It is an error to set body on a job with an incompatible HttpMethod. A base64-encoded string.

This map contains the header field names and values. Repeated headers are not supported, but a header value can contain commas.

Which HTTP method to use for the request.

Contains information needed for generating an OAuth token. This type of authorization should be used when sending requests to a GCP endpoint. Structure is documented below.

Contains information needed for generating an OpenID Connect token. This type of authorization should be used when sending requests to third party endpoints or Cloud Run. Structure is documented below.

The full URI path that the request will be sent to.

HTTP request body. A request body is allowed only if the HTTP method is POST, PUT, or PATCH. It is an error to set body on a job with an incompatible HttpMethod. A base64-encoded string.

This map contains the header field names and values. Repeated headers are not supported, but a header value can contain commas.

Which HTTP method to use for the request.

Contains information needed for generating an OAuth token. This type of authorization should be used when sending requests to a GCP endpoint. Structure is documented below.

Contains information needed for generating an OpenID Connect token. This type of authorization should be used when sending requests to third party endpoints or Cloud Run. Structure is documented below.

The full URI path that the request will be sent to.

HTTP request body. A request body is allowed only if the HTTP method is POST, PUT, or PATCH. It is an error to set body on a job with an incompatible HttpMethod. A base64-encoded string.

This map contains the header field names and values. Repeated headers are not supported, but a header value can contain commas.

Which HTTP method to use for the request.

Contains information needed for generating an OAuth token. This type of authorization should be used when sending requests to a GCP endpoint. Structure is documented below.

Contains information needed for generating an OpenID Connect token. This type of authorization should be used when sending requests to third party endpoints or Cloud Run. Structure is documented below.

The full URI path that the request will be sent to.

HTTP request body. A request body is allowed only if the HTTP method is POST, PUT, or PATCH. It is an error to set body on a job with an incompatible HttpMethod. A base64-encoded string.

This map contains the header field names and values. Repeated headers are not supported, but a header value can contain commas.

Which HTTP method to use for the request.

Contains information needed for generating an OAuth token. This type of authorization should be used when sending requests to a GCP endpoint. Structure is documented below.

Contains information needed for generating an OpenID Connect token. This type of authorization should be used when sending requests to third party endpoints or Cloud Run. Structure is documented below.

The full URI path that the request will be sent to.

HTTP request body. A request body is allowed only if the HTTP method is POST, PUT, or PATCH. It is an error to set body on a job with an incompatible HttpMethod. A base64-encoded string.

This map contains the header field names and values. Repeated headers are not supported, but a header value can contain commas.

Which HTTP method to use for the request.

Contains information needed for generating an OAuth token. This type of authorization should be used when sending requests to a GCP endpoint. Structure is documented below.

Contains information needed for generating an OpenID Connect token. This type of authorization should be used when sending requests to third party endpoints or Cloud Run. Structure is documented below.

The full URI path that the request will be sent to.

HTTP request body. A request body is allowed only if the HTTP method is POST, PUT, or PATCH. It is an error to set body on a job with an incompatible HttpMethod. A base64-encoded string.

This map contains the header field names and values. Repeated headers are not supported, but a header value can contain commas.

Which HTTP method to use for the request.

Contains information needed for generating an OAuth token. This type of authorization should be used when sending requests to a GCP endpoint. Structure is documented below.

Contains information needed for generating an OpenID Connect token. This type of authorization should be used when sending requests to third party endpoints or Cloud Run. Structure is documented below.

Service account email to be used for generating OAuth token. The service account must be within the same project as the job.

OAuth scope to be used for generating OAuth access token. If not specified, "https://www.googleapis.com/auth/cloud-platform" will be used.

Service account email to be used for generating OAuth token. The service account must be within the same project as the job.

OAuth scope to be used for generating OAuth access token. If not specified, "https://www.googleapis.com/auth/cloud-platform" will be used.

Service account email to be used for generating OAuth token. The service account must be within the same project as the job.

OAuth scope to be used for generating OAuth access token. If not specified, "https://www.googleapis.com/auth/cloud-platform" will be used.

Service account email to be used for generating OAuth token. The service account must be within the same project as the job.

OAuth scope to be used for generating OAuth access token. If not specified, "https://www.googleapis.com/auth/cloud-platform" will be used.

Service account email to be used for generating OAuth token. The service account must be within the same project as the job.

OAuth scope to be used for generating OAuth access token. If not specified, "https://www.googleapis.com/auth/cloud-platform" will be used.

Service account email to be used for generating OAuth token. The service account must be within the same project as the job.

OAuth scope to be used for generating OAuth access token. If not specified, "https://www.googleapis.com/auth/cloud-platform" will be used.

Service account email to be used for generating OAuth token. The service account must be within the same project as the job.

Audience to be used when generating OIDC token. If not specified, the URI specified in target will be used.

Service account email to be used for generating OAuth token. The service account must be within the same project as the job.

Audience to be used when generating OIDC token. If not specified, the URI specified in target will be used.

Service account email to be used for generating OAuth token. The service account must be within the same project as the job.

Audience to be used when generating OIDC token. If not specified, the URI specified in target will be used.

Service account email to be used for generating OAuth token. The service account must be within the same project as the job.

Audience to be used when generating OIDC token. If not specified, the URI specified in target will be used.

Service account email to be used for generating OAuth token. The service account must be within the same project as the job.

Audience to be used when generating OIDC token. If not specified, the URI specified in target will be used.

Service account email to be used for generating OAuth token. The service account must be within the same project as the job.

Audience to be used when generating OIDC token. If not specified, the URI specified in target will be used.

The full resource name for the Cloud Pub/Sub topic to which messages will be published when a job is delivered. ~>NOTE: The topic name must be in the same format as required by PubSub's PublishRequest.name, e.g. projects/my-project/topics/my-topic.

Attributes for PubsubMessage. Pubsub message must contain either non-empty data, or at least one attribute.

The message payload for PubsubMessage. Pubsub message must contain either non-empty data, or at least one attribute. A base64-encoded string.

The full resource name for the Cloud Pub/Sub topic to which messages will be published when a job is delivered. ~>NOTE: The topic name must be in the same format as required by PubSub's PublishRequest.name, e.g. projects/my-project/topics/my-topic.

Attributes for PubsubMessage. Pubsub message must contain either non-empty data, or at least one attribute.

The message payload for PubsubMessage. Pubsub message must contain either non-empty data, or at least one attribute. A base64-encoded string.

The full resource name for the Cloud Pub/Sub topic to which messages will be published when a job is delivered. ~>NOTE: The topic name must be in the same format as required by PubSub's PublishRequest.name, e.g. projects/my-project/topics/my-topic.

Attributes for PubsubMessage. Pubsub message must contain either non-empty data, or at least one attribute.

The message payload for PubsubMessage. Pubsub message must contain either non-empty data, or at least one attribute. A base64-encoded string.

The full resource name for the Cloud Pub/Sub topic to which messages will be published when a job is delivered. ~>NOTE: The topic name must be in the same format as required by PubSub's PublishRequest.name, e.g. projects/my-project/topics/my-topic.

Attributes for PubsubMessage. Pubsub message must contain either non-empty data, or at least one attribute.

The message payload for PubsubMessage. Pubsub message must contain either non-empty data, or at least one attribute. A base64-encoded string.

The full resource name for the Cloud Pub/Sub topic to which messages will be published when a job is delivered. ~>NOTE: The topic name must be in the same format as required by PubSub's PublishRequest.name, e.g. projects/my-project/topics/my-topic.

Attributes for PubsubMessage. Pubsub message must contain either non-empty data, or at least one attribute.

The message payload for PubsubMessage. Pubsub message must contain either non-empty data, or at least one attribute. A base64-encoded string.

The full resource name for the Cloud Pub/Sub topic to which messages will be published when a job is delivered. ~>NOTE: The topic name must be in the same format as required by PubSub's PublishRequest.name, e.g. projects/my-project/topics/my-topic.

Attributes for PubsubMessage. Pubsub message must contain either non-empty data, or at least one attribute.

The message payload for PubsubMessage. Pubsub message must contain either non-empty data, or at least one attribute. A base64-encoded string.

The maximum amount of time to wait before retrying a job after it fails. A duration in seconds with up to nine fractional digits, terminated by 's'.

The time between retries will double maxDoublings times. A job's retry interval starts at minBackoffDuration, then doubles maxDoublings times, then increases linearly, and finally retries retries at intervals of maxBackoffDuration up to retryCount times.

The time limit for retrying a failed job, measured from time when an execution was first attempted. If specified with retryCount, the job will be retried until both limits are reached. A duration in seconds with up to nine fractional digits, terminated by 's'.

The minimum amount of time to wait before retrying a job after it fails. A duration in seconds with up to nine fractional digits, terminated by 's'.

The number of attempts that the system will make to run a job using the exponential backoff procedure described by maxDoublings. Values greater than 5 and negative values are not allowed.

The maximum amount of time to wait before retrying a job after it fails. A duration in seconds with up to nine fractional digits, terminated by 's'.

The time between retries will double maxDoublings times. A job's retry interval starts at minBackoffDuration, then doubles maxDoublings times, then increases linearly, and finally retries retries at intervals of maxBackoffDuration up to retryCount times.

The time limit for retrying a failed job, measured from time when an execution was first attempted. If specified with retryCount, the job will be retried until both limits are reached. A duration in seconds with up to nine fractional digits, terminated by 's'.

The minimum amount of time to wait before retrying a job after it fails. A duration in seconds with up to nine fractional digits, terminated by 's'.

The number of attempts that the system will make to run a job using the exponential backoff procedure described by maxDoublings. Values greater than 5 and negative values are not allowed.

The maximum amount of time to wait before retrying a job after it fails. A duration in seconds with up to nine fractional digits, terminated by 's'.

The time between retries will double maxDoublings times. A job's retry interval starts at minBackoffDuration, then doubles maxDoublings times, then increases linearly, and finally retries retries at intervals of maxBackoffDuration up to retryCount times.

The time limit for retrying a failed job, measured from time when an execution was first attempted. If specified with retryCount, the job will be retried until both limits are reached. A duration in seconds with up to nine fractional digits, terminated by 's'.

The minimum amount of time to wait before retrying a job after it fails. A duration in seconds with up to nine fractional digits, terminated by 's'.

The number of attempts that the system will make to run a job using the exponential backoff procedure described by maxDoublings. Values greater than 5 and negative values are not allowed.

The maximum amount of time to wait before retrying a job after it fails. A duration in seconds with up to nine fractional digits, terminated by 's'.

The time between retries will double maxDoublings times. A job's retry interval starts at minBackoffDuration, then doubles maxDoublings times, then increases linearly, and finally retries retries at intervals of maxBackoffDuration up to retryCount times.

The time limit for retrying a failed job, measured from time when an execution was first attempted. If specified with retryCount, the job will be retried until both limits are reached. A duration in seconds with up to nine fractional digits, terminated by 's'.

The minimum amount of time to wait before retrying a job after it fails. A duration in seconds with up to nine fractional digits, terminated by 's'.

The number of attempts that the system will make to run a job using the exponential backoff procedure described by maxDoublings. Values greater than 5 and negative values are not allowed.

The maximum amount of time to wait before retrying a job after it fails. A duration in seconds with up to nine fractional digits, terminated by 's'.

The time between retries will double maxDoublings times. A job's retry interval starts at minBackoffDuration, then doubles maxDoublings times, then increases linearly, and finally retries retries at intervals of maxBackoffDuration up to retryCount times.

The time limit for retrying a failed job, measured from time when an execution was first attempted. If specified with retryCount, the job will be retried until both limits are reached. A duration in seconds with up to nine fractional digits, terminated by 's'.

The minimum amount of time to wait before retrying a job after it fails. A duration in seconds with up to nine fractional digits, terminated by 's'.

The number of attempts that the system will make to run a job using the exponential backoff procedure described by maxDoublings. Values greater than 5 and negative values are not allowed.

The maximum amount of time to wait before retrying a job after it fails. A duration in seconds with up to nine fractional digits, terminated by 's'.

The time between retries will double maxDoublings times. A job's retry interval starts at minBackoffDuration, then doubles maxDoublings times, then increases linearly, and finally retries retries at intervals of maxBackoffDuration up to retryCount times.

The time limit for retrying a failed job, measured from time when an execution was first attempted. If specified with retryCount, the job will be retried until both limits are reached. A duration in seconds with up to nine fractional digits, terminated by 's'.

The minimum amount of time to wait before retrying a job after it fails. A duration in seconds with up to nine fractional digits, terminated by 's'.

The number of attempts that the system will make to run a job using the exponential backoff procedure described by maxDoublings. Values greater than 5 and negative values are not allowed.