This is the action that will be executed by the schedule.
The OCID of the compartment in which the schedule is created
These are defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags.
Example: {@code {\"Operations\": {\"CostCenter\": \"42\"}}}
This is the description of the schedule.
This is a user-friendly name for the schedule. It does not have to be unique, and it's changeable.
These are free-form tags for this resource. Each tag is a simple key-value pair with no predefined name, type, or namespace. For more information, see Resource Tags.
Example: {@code {\"Department\": \"Finance\"}}
The OCID of the schedule
This is the status of the last work request.
This is the current state of the schedule.
This is the frequency of recurrence of a schedule. The frequency field can either conform to RFC-5545 formatting or UNIX cron formatting for recurrences, based on the value specified by the recurrenceType field.
Type of recurrence of a schedule
This is a list of resources filters. The schedule will be applied to resources matching all of them.
This is the list of resources to which the scheduled operation is applied.
These are system tags for this resource. Each key is predefined and scoped to a namespace.
Example: {@code {\"orcl-cloud\": {\"free-tier-retained\": \"true\"}}}
This is the date and time the schedule was created, in the format defined by RFC 3339.
Example: {@code 2016-08-25T21:10:29.600Z}
This is the date and time the schedule ends, in the format defined by RFC 3339
Example: {@code 2016-08-25T21:10:29.600Z}
This is the date and time the schedule runs last time, in the format defined by RFC 3339.
Example: {@code 2016-08-25T21:10:29.600Z}
This is the date and time the schedule run the next time, in the format defined by RFC 3339.
Example: {@code 2016-08-25T21:10:29.600Z}
This is the date and time the schedule starts, in the format defined by RFC 3339
Example: {@code 2016-08-25T21:10:29.600Z}
This is the date and time the schedule was updated, in the format defined by RFC 3339.
Example: {@code 2016-08-25T21:10:29.600Z}
This is the summary information about a schedule.