Because jobs can potentially take a long time to complete, they execute asynchronously and can be polled for their status. Shorter actions, such as listing resources or getting metadata are not managed by a job resource.
When you perform actions in the web UI or CLI, a job resource is automatically created and run.
When you use the API, you start a job by calling the
method using a unique job ID that is
generated by your client code.