When you start a Run in Domino, the Run will move through several lifecycle states.
This page describes what these different stages mean.
QueuedThe Run is waiting for a machine of your specified hardware tier tobecome available. If one is available, it will quickly leave thisstate. However if no slots are available, it can take several minutesto start up a new machine.
ScheduledThis is when the dispatcher has requested an executorto process the Run and the executor acknowledges this request, buthasn’t begun the processing yet. A Run only remains in this state fora few seconds.
PreparingYour project files are being copied to the executor where your codewill run. Depending on the size of your data and the number of filesin your project, this might finish quickly, or may take a while. Filesare cached when possible, so if you start a Run on a hardware tier youused recently with the same project, this may be quick, even forprojects with large files.
BuildingIf you are using a custom environment,you may need to wait for the Docker image to build. This is cachedwhenever possible, so subsequent Runs on the same hardware tier mayskip this step.
PullingWhen your Docker image has been saved to a network-attachedrepository, this state indicates we are fetching the image.
RunningYour code is executing. You can view the console output and resourceusage on the Jobs or Workspaces dashboard.
FinishingYour Run has completed, and any file changes are being copied backto the Domino file store.
SucceededYour Run has finished without error.
StopRequestedThe request to stop your Run has been received.
StoppingIf you manually stop your Run, it will enter this state while any newor updated files are synced back to the project.
StoppedThe Run has been manually stopped.
FailedYour Run did not complete due to a problem with your code.
ErrorSome problem outside of your code caused the Run to terminate.