Namespace Schedule

The OCID of the compartment where you want to create the schedule.

The OCID of the user who created the schedule.

Defined tags for this resource. Each key is predefined and scoped to a namespace. See Resource Tags. Example: {@code {"Operations": {"CostCenter": "42"}}}

A short description of the schedule.

A user-friendly display name for the resource. Avoid entering confidential information.

Free-form tags for this resource. Each tag is a simple key-value pair with no predefined name, type, or namespace. See Resource Tags. Example: {@code {"Department": "Finance"}}

The OCID of the schedule.

Details about the action performed by the last schedule execution. Example: {@code Invoked ML Application trigger.}

A message describing the current state in more detail.

The current state of the schedule. Example: {@code ACTIVE}

The OCID of the project associated with the schedule.

Usage of system tag keys. These predefined keys are scoped to namespaces. Example: {@code {"orcl-cloud": {"free-tier-retained": "true"}}}

The date and time the schedule was created. Format is defined by RFC3339. Example: {@code 2022-08-05T01:02:29.600Z}

The last schedule execution time. Format is defined by RFC3339. Example: {@code 2022-08-05T01:02:29.600Z}

The next scheduled execution time for the schedule. Format is defined by RFC3339. Example: {@code 2022-08-05T01:02:29.600Z}

The date and time the schedule was updated. Format is defined by RFC3339. Example: {@code 2022-09-05T01:02:29.600Z}