OCID of the user who created the job execution.
The key of the associated data entity resource.
Error code returned from the job execution or null if job is still running or didn't return an error.
Error message returned from the job execution or null if job is still running or didn't return an error.
An identifier used for log message correlation.
If the job is an external process, then a URL of the job for accessing this resource and its status.
The unique key of the parent job.
Type of the job execution.
Unique key of the job execution resource.
Status of the job execution, such as running, paused, or completed.
The unique key of the parent execution or null if this job execution has no parent.
Process identifier related to the job execution if the job is an external job.
A map of maps that contains the execution context properties which are specific to a job execution. Each job execution may define it's set of required and optional properties. The map keys are category names and the values are maps of property name to property value. Every property is contained inside of a category. Most job executions have required properties within the "default" category. Example: {@code {"properties": { "default": { "host": "host1", "port": "1521", "database": "orcl"}}}}
The unique key of the triggering external scheduler resource or null if this job execution is not externally triggered.
Sub-type of this job execution.
The date and time the job execution was created, in the format defined by RFC3339. Example: {@code 2019-03-25T21:10:29.600Z}
Time that the job execution ended or null if it hasn't yet completed. An RFC3339 formatted datetime string.
Time that job execution started. An RFC3339 formatted datetime string.
OCID of the user who updated the job execution.
URI to the job execution instance in the API.
A job execution is a unit of work being executed on behalf of a job.