Managing Job Runs
Learn about job run details, canceling, and cloning them.
Job Run Details
The details page for the job run opens and displays the following information. Access the various resources associated with the job run by selecting their links or tabs.
- Who created the job run.
- When the job run was accepted, started and finished.
- Job run OCID.
- Logging details if it was enabled.
- Infrastructure configuration including the VM shape name, the subnet OCID, and the storage size.
Job run details also include the following, when they exist.
- Runtime configuration
Command line arguments, maximum runtime minutes, and environment variables that were specified. Both the default and override configurations are displayed.
- Storage mounts
The storage mounts can't be changed in a job run though can be edited in the job.
- Environment configuration (custom environment variable keys)
- Monitoring
- Tags
Canceling Job Runs
Only job runs that are in ACCEPTED, IN_PROGRESS, or NEEDS_ATTENTION states can be canceled.
You can either select the job run's name or the , and select Cancel to cancel the job run.
Cloning Job Runs
In the Console, you can clone a job run to use the same run as a basis for a new run that you want to change configurations to get different results. Cloning lets you to start several jobs runs to run in succession with varied results.
Cloning is only available in the Console.
Using the API
Use the following operations to manage job runs:
For information about using the API and signing requests, see REST APIs and Security Credentials. For information about SDKs, see Software Development Kits and Command Line Interface.