Class Job (1.3.2)

Configuration for a job. The maximum allowed size for a job is 100KB. .. attribute:: name

Optionally caller-specified in [CreateJob][google.cloud.schedu ler.v1beta1.CloudScheduler.CreateJob], after which it becomes output only. The job name. For example: projects/PROJECT_ID/locations/LOCATION_ID/jobs/JOB_ID. - PROJECT_ID can contain letters ([A-Za-z]), numbers ([0-9]), hyphens (-), colons (:), or periods (.). For more information, see Identifying projects <https://cloud.google.com/resource-manager/docs/creating- managing-projects#identifying_projects>_ - LOCATION_ID is the canonical ID for the job's location. The list of available locations can be obtained by calling [ListLocatio ns][google.cloud.location.Locations.ListLocations]. For more information, see https://cloud.google.com/about/locations/. - JOB_ID can contain only letters ([A-Za-z]), numbers ([0-9]), hyphens (-), or underscores (\). The maximum length is 500 characters.

Required. Delivery settings containing destination and parameters.

App Engine HTTP target.

Required, except when used with [UpdateJob][google.cloud.sched uler.v1beta1.CloudScheduler.UpdateJob]. Describes the schedule on which the job will be executed. The schedule can be either of the following types: - Crontab <http://en.wikipedia.org/wiki/Cron#Overview> - English- like schedule <https://cloud.google.com/scheduler/docs/configuring/cron-job- schedules> As a general rule, execution n + 1 of a job will not begin until execution n has finished. Cloud Scheduler will never allow two simultaneously outstanding executions. For example, this implies that if the n+1\ th execution is scheduled to run at 16:00 but the n\ th execution takes until 16:15, the n+1\ th execution will not start until 16:15. A scheduled start time will be delayed if the previous execution has not ended when its scheduled time occurs. If [retry_count][google.cloud.schedul er.v1beta1.RetryConfig.retry_count] > 0 and a job attempt fails, the job will be tried a total of [retry_count][google. cloud.scheduler.v1beta1.RetryConfig.retry_count] times, with exponential backoff, until the next scheduled start time.

Output only. The creation time of the job.

Output only. The response from the target for the last attempted execution.

Output only. The time the last job attempt started.

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][google.cloud.scheduler.v1beta1.Job.http_target], between 15 seconds and 30 minutes. - For [App Engine HTTP targets][google.cloud.scheduler.v1beta1.Job.app_engine_http _target], between 15 seconds and 24 hours. - For [PubSub targets][google.cloud.scheduler.v1beta1.Job.pubsub_target], this field is ignored.