Introduction to job

A job executes the code once, and if it completes successfully, the job is marked as Succeeded. If it fails, the job can be configured to retry several times. The job is marked as' Failed' if it does not successfully finish even after the configured number of retries. The compute and memory resources are released once the job is completed, and hence we don't incur any cost once the job completes.

Jobs can be triggered in multiple ways:

1. Manual: This is good for ad hoc use cases and can be triggered manually. An example can be a model training job which can be run when needed.
2. Schedule: A job can be triggered on a schedule like daily, weekly, or at 9 AM every Monday. An example of this can be a batch inference job running every morning at 8 AM on the previous day's incoming data