Stopping active runtimes
You should stop all active runtimes when you no longer need them to prevent consuming extra capacity unit hours (CUHs).
Project users with Admin role can stop all runtimes in the project. Users added to the project with Editor role can stop the runtimes they started, but can’t stop other project users’ runtimes. Users added to the project with the viewer role can’t see the runtimes in the project.
You can stop runtimes from:
- The Environment Runtimes page, which lists all active runtimes across all projects for your account by clicking Manage > Environment Runtimes
- From the Environments page of a project, which list the active runtimes for a specific project by clicking the Environments tab for a project.
Default idle timeout
All default environment runtimes are shutdown automatically if they have been idle for longer than one hour.
If you have a Lite or Standard v1 service plan, your environment runtimes are shutdown automatically after 12 hours of continuous use.
Stopping the notebook kernel doesn’t stop the environment runtime in which the kernel is started because other kernels could still be active in that runtime. Only stop a runtime if you are sure that no kernels are active.
Runtimes for scheduled notebooks are automatically shut down after the scheduled job has completed if the runtime isn’t also shared by another notebook. For example, if you schedule to run a notebook once a day for 2 months, the runtime instance will be activated every day for the duration of the scheduled job and deactivated again after the job has finished.
Spark idle timeout
All Spark runtimes are automatically stopped after 3 hours of inactivity.
GPU idle timeout
All GPU runtimes are automatically stopped after 1 hour of inactivity for Lite plan users and after 3 hours of inactivity for paid plan users.