Job status

A job’s status could be any of the following:

Status	Description	How the state relates to the client
Running	Normal operational state of a job. A job enters the Running state as soon as it is created. The system schedules pending tasks for processing, if there are resources available.	The client can send new tasks.
Done	Successful end state of a job.	The client cannot send new tasks.
Suspended	A job enters the Suspended state if a user performs an administrative operation to forcefully suspend the job. When a job is suspended, any running tasks are given a grace period (suspendGracePeriod in the application profile) to finish. If they do not finish before the grace period, the service instance on which they are running is killed, the task is re-queued and placed in the Pending state. No pending tasks are scheduled until the job is resumed. All re-queued tasks are rerun when the job resumes.	There is no impact to the client. The client can send new tasks.
Aborted	A job could end in the Aborted state if: A user terminated the job The client lost connection with the Application Manager and the abortSessionIfClientDisconnect parameter is set to true in the application profile At least one task failed and the abortSessionIfTaskFail parameter is set to true in the application profile Service event occurred (where actionOnWorkload is set to fail) while executing SessionEnter or SessionUpdate methods Job exceeded its sessionRetryLimit, as defined in the application profile, by experiencing service events where actionOnWorkload is set to retry when executing SessionEnter or SessionUpdate methods. Note: The retry count for both of these methods are considered together. For example, if SessionEnter fails once and SessionUpdate fails twice, then the job rerun count is equal to 3.	The client receives an exception to indicate that the job was aborted. It is no longer able to operate on the job.