You might be curious to know what our various job statuses mean. You'll encounter the different job statuses each time you build and submit a job to Nimbix Cloud.
Typically when submitting your job to the Nimbix Cloud, the flow of statuses will be ordered like below. Keep in mind; the statues will appear on your dashboard. There are a few exceptions to the statuses below, which I'll describe in detail below.
4. Shutting Down
Below are each job statuses, along with a little more explanation behind what each of these means.
Queued - Your job has been received and is waiting for available hardware. You are not being billed for machine time while the job is in this state. If you press the "abort" button while Queued, the job will not run, and there is no cost to the user. Typically during this phase, resources, i.e., machines, fabric, storage, etc. are being marshaled together, and the job is being assembled. If your job is in this status for more than 5 minutes, there's the possibility your job is queueing awaiting for additional machines to free-up.
Starting - At this point resources have been allocated to your job, and the Nimbix Cloud is putting the final touches on the job, before handing it over to you.
Processing - Your dedicated machines have been allocated to your job. Your application is now running, and if it is interactive, you can connect to it. Jobs only bill machine time while a job is in this state.
Completed - Your application exited successfully. This occurs when closing out an application window, terminating from the portal, or completing a batch script.
Completed with Error - Your application has encountered errors while running. Please inspect the job's output and open a support ticket at firstname.lastname@example.org if you are unsure of the cause.
If you have any additional questions or comments on the above, please reach out to us at email@example.com.