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.

Stop default runtimes

You can stop default runtimes that are billed against your user account from the Environment Runtimes page, which lists all active runtime across all projects for your account. Choose Manage > Environment Runtimes.

You can also stop runtimes for a specific project from the Environments page of that project.

Note that stopping a notebook kernel doesn’t stop the environment runtime in which the kernel is started because other kernels could still be active in that runtime. This runtime will be stopped automatically after an idle time of one hour.

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.

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.

Stop Spark runtimes

You can stop Spark runtimes that are billed against your user account from the Environment Runtimes page, which lists all active runtime across all projects for your account. Choose Manage > Environment Runtimes.

You can also stop Spark runtimes for a specific project from the Environments page of that project.

All Spark runtimes are automatically stopped after 3 hours of inactivity.