Why is my job run not completing?

When using the console, you submit a job and the job run does not complete.

When using the CLI, after you submit a job, the job run does not complete. You can confirm this result by running the ibmcloud ce jobrun get command to display the details of the job run, and the job run status result does not include the following output:

Status:                True
Type:                  Complete

If your job run did not complete, determine whether one of the following cases is true.

The job run requires more time to complete.
The image that is used by your job run does not exist.
The container registry quota is exceeded or the registry needs authentication.
The environment variable parameters that are required by the job run are not specified.
The commands or arguments that are passed to the job run are not valid.

Try one of these solutions.

Check that enough time is specified for the job to run.
- From the console, from your job page, click Submit Job to run a job that is based on the selected job and its defined properties. Check that the Job timeout value is set properly and specifies enough time for the job run to complete.
- With the CLI, check that the --maxexecutiontime MAX_TIME option is set properly and enough time is specified for the job run to complete.
Check that the image that is used by your job run exists and is referred to correctly.
- From the console, from your job page, check that the image that is specified for Image reference is correct and confirm that this image exists in the container registry.
- With the CLI, use the ibmcloud ce jobrun get command to display details of your job run, which includes the name of the image. Confirm that you are using an image that exists.
Check for an ImagePullBackOff error by running the ibmcloud ce jobrun events --jobrun JOBRUN_NAME command; for example,
```
ibmcloud ce jobrun events --jobrun myjobrun
```
- If the error in the events is similar to the following message, this error indicates that the registry quota is exceeded. Consider upgrading your plan. For information about IBM Cloud Container Registry service plans and quota limits, see About IBM Cloud Container Registry.
```
403 Forbidden - Server message: denied: You have exceeded your pull traffic quota for the current month. Review your pull traffic quota and pricing plan.
```
- If the error in the events is similar to the following message, this error indicates that access to the registry does not exist or might require authorization. Check that your credentials have appropriate access to the registry.
```
Failed to pull image "<image_name>": rpc error: code = Unknown desc = failed to pull and unpack image "<image_name:image_tag>": failed to resolve reference <image_name:image_tag>": pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed.
```
View details of the submitted job run.
- From the console, view details of your submitted job run by clicking the name of your job run in the Job runs tab on your job page. From the submitted job run details page, you can review any environment variables that are set and check that the environment variables are correct.
- With the CLI, use the ibmcloud ce jobrun get command and review the results for the following items:
  - Check to see whether any environment variables that are set by using the --env KEY=VALUE, --env-from-secret SECRET_NAME, and --env-from-configmap CONFIGMAP_NAME options are correct in the job run details.
  - Use the ibmcloud ce secret get --name SECRET_NAME and ibmcloud ce configmap get --name CONFIGMAP_NAME commands to check that any environment variable that is stored in the secret and configmap does exist.
Verify that the commands and arguments are valid for the job run.
- From the console, view details of the submitted job run in the console by clicking the name of your job run in the Job runs tab on your job page. The submitted job details page lists any commands or arguments that are defined for the submitted job run. The sequence in the commands and arguments is important.
- With the CLI, use the view details of the submitted job run by using the ibmcloud ce jobrun get command. The sequence in the commands and arguments is important.

If these solutions do not solve your issue, for further debugging, try retrieving the logs or the system event information for your job run. For more information, see How do I get logs for my job run instances? and How do I get system event information for my job run instances? (CLI).

For more information about running jobs, see Running jobs.