If you have the Admin role or Editor in a project, you can perform management tasks for environments.

• Create an environment template
• Customize an environment template
• Stop active runtimes
• Promote an environment template to a space
• Track capacity unit consumption of runtimes

Stop active runtimes

You should stop all active runtimes when you no longer need them to prevent consuming extra capacity unit hours (CUHs).

Jupyter notebook runtimes are started per user and not per notebook. Stopping a notebook kernel doesn't stop the environment runtime in which the kernel is started because you could have started other notebooks in the same environment. You should only stop a notebook runtime if you are sure that no other notebook kernels are active.

Only runtimes that are started for jobs are automatically shut down after the scheduled job has completed. 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.

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 Administration > Environment runtimes from the watsonx.ai Studio navigation menu.
• Under Tool runtimes on the Environments page on the Manage tab of your project, which lists the active runtimes for a specific project.
• The Environments page when you click the Notebook Info icon from the notebook toolbar in the notebook editor. You can stop the runtime under Runtime status.

Idle timeouts for:

• Jupyter notebook runtimes
• Spark runtimes for notebooks and Data Refinery
• Notebook with GPU runtimes
• RStudio runtimes