Skip to main content
Section ID: DOC-API-MODEL-schema-1ld0l8rmvg#overview

Schedule

Schedule is the canonical representation of a scheduled job.

Creating any schedule type returns the Schedule resource directly, with the same shape used by get, pause and resume operations.

triggerCount: Cumulative firings.

failureCount: Cumulative failed first attempts; a later successful retry does not erase the earlier failure.

consecutiveFailureCount: Current sequence of failed firings; a successful attempt resets it. This counter drives auto-pause.

Zero-valued counters can be omitted. Nonzero 64-bit counters are decimal JSON strings; preserve their integer precision.

Meaning and usage​

Section ID: DOC-API-MODEL-schema-1ld0l8rmvg#meaning

See the definition above.

Usage profiles​

Section ID: DOC-API-MODEL-schema-1ld0l8rmvg#fields

UsageFields and validation
In responsesView fields

In responses​

Section ID: DOC-API-MODEL-schema-1ld0l8rmvg#response

API JSON uses JSON field names (camelCase).

FieldTypePresenceMeaning
Section ID: DOC-API-MODEL-schema-1ld0l8rmvg#field-scheduleidSection ID: DOC-API-MODEL-schema-1ld0l8rmvg#response-field-scheduleidscheduleIdstringOptionalServer-assigned identifier of the scheduled job, prefixed with "sched_".
Section ID: DOC-API-MODEL-schema-1ld0l8rmvg#field-tenantidSection ID: DOC-API-MODEL-schema-1ld0l8rmvg#response-field-tenantidtenantIdstringOptionalIdentifier of the tenant that owns or scopes this record.
Section ID: DOC-API-MODEL-schema-1ld0l8rmvg#field-projectidSection ID: DOC-API-MODEL-schema-1ld0l8rmvg#response-field-projectidprojectIdstringOptionalIdentifier of the project within the tenant that scopes this record.
Section ID: DOC-API-MODEL-schema-1ld0l8rmvg#field-ownersubjectSection ID: DOC-API-MODEL-schema-1ld0l8rmvg#response-field-ownersubjectownerSubjectstringOptionalSubject identifier of the owning user or service account.
Section ID: DOC-API-MODEL-schema-1ld0l8rmvg#field-nameSection ID: DOC-API-MODEL-schema-1ld0l8rmvg#response-field-namenamestringOptionalHuman-readable name assigned to the scheduled job.
Section ID: DOC-API-MODEL-schema-1ld0l8rmvg#field-descriptionSection ID: DOC-API-MODEL-schema-1ld0l8rmvg#response-field-descriptiondescriptionstringOptionalHuman-readable explanation of the scheduled job.
Section ID: DOC-API-MODEL-schema-1ld0l8rmvg#field-scheduletypeSection ID: DOC-API-MODEL-schema-1ld0l8rmvg#response-field-scheduletypescheduleTypestring (SCHEDULE_TYPE_CRON, SCHEDULE_TYPE_ONCE, SCHEDULE_TYPE_RECURRING_INTERVAL) or integer (int32)Optional; explicit presenceSchedule type and expression.
Section ID: DOC-API-MODEL-schema-1ld0l8rmvg#field-cronexpressionSection ID: DOC-API-MODEL-schema-1ld0l8rmvg#response-field-cronexpressioncronExpressionstringOptionalCron expression. Populated when schedule_type is SCHEDULE_TYPE_CRON.
Section ID: DOC-API-MODEL-schema-1ld0l8rmvg#field-timezoneSection ID: DOC-API-MODEL-schema-1ld0l8rmvg#response-field-timezonetimezonestringOptionalIANA timezone for cron evaluation. Default "UTC".
Section ID: DOC-API-MODEL-schema-1ld0l8rmvg#field-scheduledatSection ID: DOC-API-MODEL-schema-1ld0l8rmvg#response-field-scheduledatscheduledAtstring (date-time)OptionalExact fire time. Populated when schedule_type is SCHEDULE_TYPE_ONCE.
Section ID: DOC-API-MODEL-schema-1ld0l8rmvg#field-intervalsecondsSection ID: DOC-API-MODEL-schema-1ld0l8rmvg#response-field-intervalsecondsintervalSecondsstring (int64)OptionalInterval between firings in seconds. Populated when schedule_type is SCHEDULE_TYPE_RECURRING_INTERVAL. Pattern: ^-?\d+$.
Section ID: DOC-API-MODEL-schema-1ld0l8rmvg#field-targetSection ID: DOC-API-MODEL-schema-1ld0l8rmvg#response-field-targettargetScheduleTargetOptionalDestination and invocation settings for the scheduled job.
Section ID: DOC-API-MODEL-schema-1ld0l8rmvg#field-stateSection ID: DOC-API-MODEL-schema-1ld0l8rmvg#response-field-statestatestring (SCHEDULE_STATUS_ACTIVE, SCHEDULE_STATUS_PAUSED, SCHEDULE_STATUS_DELETED) or integer (int32)Optional; explicit presenceLifecycle status controlling whether the scheduled job can trigger.
Section ID: DOC-API-MODEL-schema-1ld0l8rmvg#field-retrypolicySection ID: DOC-API-MODEL-schema-1ld0l8rmvg#response-field-retrypolicyretryPolicyRetryPolicyOptionalAttempt limits and backoff settings for the scheduled target.
Section ID: DOC-API-MODEL-schema-1ld0l8rmvg#field-metadataSection ID: DOC-API-MODEL-schema-1ld0l8rmvg#response-field-metadatametadataMap from string to JSON valueOptionalApplication-defined JSON metadata attached to the scheduled job.
Section ID: DOC-API-MODEL-schema-1ld0l8rmvg#field-autopausethresholdSection ID: DOC-API-MODEL-schema-1ld0l8rmvg#response-field-autopausethresholdautoPauseThresholdstring (int64)OptionalSee meaning below. Pattern: ^-?\d+$.
Section ID: DOC-API-MODEL-schema-1ld0l8rmvg#field-externalidSection ID: DOC-API-MODEL-schema-1ld0l8rmvg#response-field-externalidexternalIdstringOptionalClient-supplied external id. Echoed back when set; empty otherwise. Optional, immutable, unique within (tenant_id, project_id) among live schedules. Never starts with the reserved system-id prefix "sched_".
Section ID: DOC-API-MODEL-schema-1ld0l8rmvg#field-createdatSection ID: DOC-API-MODEL-schema-1ld0l8rmvg#response-field-createdatcreatedAtstring (date-time)OptionalTime at which the scheduled job was created.
Section ID: DOC-API-MODEL-schema-1ld0l8rmvg#field-createdbysubjectSection ID: DOC-API-MODEL-schema-1ld0l8rmvg#response-field-createdbysubjectcreatedBySubjectstringOptionalSubject identifier recorded when the schedule was created.
Section ID: DOC-API-MODEL-schema-1ld0l8rmvg#field-updatedatSection ID: DOC-API-MODEL-schema-1ld0l8rmvg#response-field-updatedatupdatedAtstring (date-time)OptionalTime this record was most recently updated.
Section ID: DOC-API-MODEL-schema-1ld0l8rmvg#field-updatedbysubjectSection ID: DOC-API-MODEL-schema-1ld0l8rmvg#response-field-updatedbysubjectupdatedBySubjectstringOptionalSubject identifier recorded when the schedule was last updated.
Section ID: DOC-API-MODEL-schema-1ld0l8rmvg#field-pausedatSection ID: DOC-API-MODEL-schema-1ld0l8rmvg#response-field-pausedatpausedAtstring (date-time)OptionalTime at which the schedule was paused.
Section ID: DOC-API-MODEL-schema-1ld0l8rmvg#field-pausedbysubjectSection ID: DOC-API-MODEL-schema-1ld0l8rmvg#response-field-pausedbysubjectpausedBySubjectstringOptionalSubject identifier recorded for the schedule pause.
Section ID: DOC-API-MODEL-schema-1ld0l8rmvg#field-pausedreasonSection ID: DOC-API-MODEL-schema-1ld0l8rmvg#response-field-pausedreasonpausedReasonstringOptionalExplanation recorded for the schedule pause.
Section ID: DOC-API-MODEL-schema-1ld0l8rmvg#field-resumedatSection ID: DOC-API-MODEL-schema-1ld0l8rmvg#response-field-resumedatresumedAtstring (date-time)OptionalTime at which the schedule was most recently resumed.
Section ID: DOC-API-MODEL-schema-1ld0l8rmvg#field-resumedbysubjectSection ID: DOC-API-MODEL-schema-1ld0l8rmvg#response-field-resumedbysubjectresumedBySubjectstringOptionalSubject identifier recorded for the schedule resume.
Section ID: DOC-API-MODEL-schema-1ld0l8rmvg#field-deletedatSection ID: DOC-API-MODEL-schema-1ld0l8rmvg#response-field-deletedatdeletedAtstring (date-time)OptionalTime at which the schedule was deleted.
Section ID: DOC-API-MODEL-schema-1ld0l8rmvg#field-deletedbysubjectSection ID: DOC-API-MODEL-schema-1ld0l8rmvg#response-field-deletedbysubjectdeletedBySubjectstringOptionalSubject identifier recorded for the schedule deletion.
Section ID: DOC-API-MODEL-schema-1ld0l8rmvg#field-lasttriggeredatSection ID: DOC-API-MODEL-schema-1ld0l8rmvg#response-field-lasttriggeredatlastTriggeredAtstring (date-time)OptionalTime when the schedule was last triggered. Trigger and failure counters advance at most once per scheduled firing on its first attempt; retrying that firing does not inflate them.
Section ID: DOC-API-MODEL-schema-1ld0l8rmvg#field-nexttriggeratSection ID: DOC-API-MODEL-schema-1ld0l8rmvg#response-field-nexttriggeratnextTriggerAtstring (date-time)OptionalTime calculated for the next scheduled trigger.
Section ID: DOC-API-MODEL-schema-1ld0l8rmvg#field-triggercountSection ID: DOC-API-MODEL-schema-1ld0l8rmvg#response-field-triggercounttriggerCountstring (int64)OptionalScheduled times that ran, cumulative for the schedule's whole life. Pattern: ^-?\d+$.
Section ID: DOC-API-MODEL-schema-1ld0l8rmvg#field-failurecountSection ID: DOC-API-MODEL-schema-1ld0l8rmvg#response-field-failurecountfailureCountstring (int64)OptionalSee meaning below. Pattern: ^-?\d+$.
Section ID: DOC-API-MODEL-schema-1ld0l8rmvg#field-consecutivefailurecountSection ID: DOC-API-MODEL-schema-1ld0l8rmvg#response-field-consecutivefailurecountconsecutiveFailureCountstring (int64)OptionalSee meaning below. Pattern: ^-?\d+$.

autoPauseThreshold

If consecutive_failure_count reaches this threshold the job is auto-paused (state PAUSED, paused_by_subject "system:auto-pause").

It is compared against consecutive_failure_count, NOT failure_count. failure_count is cumulative for the schedule's whole life, so a healthy schedule that collects scattered failures over months would eventually exceed any threshold and pause itself forever.

A stored threshold of 0 disables auto-pause; otherwise the threshold is from 3 through 100. The public create request uses 0 or omission to select the default of 10, and the public update request uses 0 or omission to leave the current threshold unchanged. These public requests do not provide a disable control.

failureCount

Scheduled times whose first attempt failed, cumulative for the schedule's whole life. A firing that fails on attempt 1 and succeeds on retry still counts here — a failure was observed.

This counter does NOT drive auto-pause. See consecutive_failure_count.

consecutiveFailureCount

Current run of consecutive failed firings. This is the counter auto_pause_threshold is compared against.

Incremented when a firing's first attempt fails; reset to 0 as soon as any attempt of any firing succeeds. So a firing that fails on attempt 1 and succeeds on retry has net zero effect here while still advancing failure_count — the target recovered, so the run is over.

A non-success terminal outcome counts as a failure, including a firing cancelled on a terminal 4xx.

Values of scheduleType​

Section ID: DOC-API-MODEL-schema-1ld0l8rmvg#response-values-scheduletype

Expression format that determines when a scheduled job fires.

ValueNo.FormMeaning
SCHEDULE_TYPE_CRON0CanonicalFire according to the configured cron expression and timezone. For example, 0 9 * * 1-5 selects 09:00 on weekdays in that timezone.
SCHEDULE_TYPE_ONCE1CanonicalFire once at the configured scheduled timestamp.
SCHEDULE_TYPE_RECURRING_INTERVAL2CanonicalFire repeatedly at the configured interval in seconds.

Values of state​

Section ID: DOC-API-MODEL-schema-1ld0l8rmvg#response-values-state

Lifecycle condition that determines whether a scheduled job may trigger: active, paused, or deleted. This is separate from the outcome of an individual scheduled-job execution.

ValueNo.FormMeaning
SCHEDULE_STATUS_ACTIVE0CanonicalThe schedule is active and can trigger at its next matching time.
SCHEDULE_STATUS_PAUSED1CanonicalThe schedule is paused and does not trigger until resumed.
SCHEDULE_STATUS_DELETED2CanonicalThe schedule has been deleted; this is a schedule condition, not an execution outcome.

Where used​

Section ID: DOC-API-MODEL-schema-1ld0l8rmvg#where-used

ReferenceRelationship
Create a scheduled jobPOST /api/v1/scheduler/create-job
Get a scheduled jobPOST /api/v1/scheduler/get-job
List scheduled jobsPOST /api/v1/scheduler/list-jobs
Pause a scheduled jobPOST /api/v1/scheduler/pause-job
Resume a scheduled jobPOST /api/v1/scheduler/resume-job
Update a scheduled jobPOST /api/v1/scheduler/update-job

Download the public reference contract.

Document ID: DOC-API-MODEL-schema-1ld0l8rmvg