When you start an execution in Domino, it moves through several states during its lifecycle.
The execution is waiting for a machine of your specified hardware tier to become available. If one is available, it quickly leaves this state. However if no slots are available, it can take several minutes to start up a new machine.
The dispatcher requested an executor to process the execution and the executor acknowledges this request, but hasn’t begun processing. An execution only remains in this state for a few seconds.
Your project files are being copied to the executor where your code will run. The time this takes depends on the size of your data and the number of files in your project. Files are cached whenever possible. Therefore, if you start an execution on a hardware tier that you used recently with the same project, this can be quick, even for projects with large files.
If you are using a custom environment, you might have to wait for the Docker image to build. This is cached whenever possible, so subsequent executions on the same hardware tier might skip this step.
When your Docker image has been saved to a network-attached repository, this state indicates that Domino is fetching the image.
Your code is executing. You can view the console output and resource usage on the Jobs or Workspaces dashboard.
Your execution has completed. File changes are being copied back to the Domino file store.
Your execution has finished without error.
The system received the request to stop your execution.
If you manually stop your execution, it enters this state while new or updated files are synced back to the project.
The execution has been manually stopped.
Your execution did not complete due to a problem with your code.
Some problem outside your code caused the execution to terminate.