gcloud beta colab schedules update - update a schedule

gcloud beta colab schedules update(SCHEDULE :--region=REGION)(--cron-schedule=CRON_SCHEDULE--display-name=DISPLAY_NAME--enable-queueing--end-time=END_TIME--max-concurrent-runs=MAX_CONCURRENT_RUNS--max-runs=MAX_RUNS--start-time=START_TIME)[GCLOUD_WIDE_FLAG …]

Schedule resource - Unique, system-generated resource name of the schedule toupdate. The arguments in this group can be used to specify the attributes ofthis resource. (NOTE) Some attributes are not given arguments in this group butcan be set in other ways.

To set theproject attribute:

• provide the argumentschedule on the command line with a fullyspecified name;
• provide the argument--project on the command line;
• set the propertycore/project.

This must be specified.

SCHEDULE

ID of the schedule or fully qualified identifier for the schedule.

To set thename attribute:

• provide the argumentschedule on the command line.

This positional argument must be specified if any of the other arguments in thisgroup are specified.

--region=REGION

Cloud region for the schedule.

To set theregion attribute:

• provide the argumentschedule on the command line with a fullyspecified name;
• provide the argument--region on the command line;
• set the propertycolab/region.

Configuration of the schedule.

At least one of these must be specified:

--cron-schedule=CRON_SCHEDULE

Cron schedule (https://en.wikipedia.org/wiki/Cron) to launch scheduled runs. Toexplicitly set a timezone to the cron tab, apply a prefix in the cron tab:"CRON_TZ=${IANA_TIME_ZONE}" or "TZ=${IANA_TIME_ZONE}". The ${IANA_TIME_ZONE} mayonly be a valid string from IANA time zone database. For example,"CRON_TZ=America/New_York 1 * * *", or "TZ=America/New_York 1 * * *".

--display-name=DISPLAY_NAME

The display name of the schedule.

--enable-queueing

Enables new scheduled runs to be queued when max_concurrent_runs limit isreached. If set to true, new runs will be queued instead of skipped.

--end-time=END_TIME

Timestamp after which no new runs can be scheduled. If specified, the schedulewill be completed when either end_time is reached or when scheduled_run_count>= max_run_count. If neither end time nor max_run_count is specified, newruns will keep getting scheduled until this Schedule is paused or deleted. Mustbe in the RFC 3339 (https://www.rfc-editor.org/rfc/rfc3339.txt) format. E.g."2026-01-01T00:00:00Z" or "2026-01-01T00:00:00-05:00"

--max-concurrent-runs=MAX_CONCURRENT_RUNS

Maximum number of runs that can be started concurrently for this Schedule. Thisis the limit for starting the scheduled requests and not the execution of thenotebook execution jobs created by the requests.

--max-runs=MAX_RUNS

The max runs for the schedule.

--start-time=START_TIME

The timestamp after which the first run can be scheduled. Defaults to theschedule creation time. Must be in the RFC 3339(https://www.rfc-editor.org/rfc/rfc3339.txt) format. E.g. "2026-01-01T00:00:00Z"or "2026-01-01T00:00:00-05:00"

Run$gcloud help for details.