Transcription format. JSON format will always be provided in addition to any formats in this list.
The OCID of the compartment where you want to create the job.
The OCID of the user who created the job.
Defined tags for this resource. Each key is predefined and scoped to a namespace. Example: {@code {"foo-namespace-1": {"bar-key-1": "value-1", "bar-key-2": "value-2"}, "foo-namespace-2": {"bar-key-1": "value-1", "bar-key-2": "value-2"}}}.
A short description of the job.
A user-friendly display name for the job.
Simple key-value pair that is applied without any predefined name, type or scope. Exists for cross-compatibility only. Example: {@code {"bar-key": "value"}}.
The OCID of the job.
A message describing the current state in more detail. For example, can be used to provide actionable information for a resource in Failed state.
The current state of the Job.
Total outstanding tasks in a job. Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.
How much progress the operation has made, vs the total amount of work that must be performed. Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.
Total successful tasks in a job. Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.
Usage of system tag keys. These predefined keys are scoped to namespaces. Example: {@code {"orcl-cloud": {"free-tier-retained": "true"}}}.
Job accepted time.
Job finished time.
Job started time.
Total tasks in a job. Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.
Time to live duration in days for Job. Job will be available till max 90 days. Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.
Description of Transcription Job.