Basic cloud app operations

Operations that can be performed on cloud apps through the Workbench web UI

Prior reading: Cloud apps overview

Purpose: This document provides detailed instructions for performing basic operations on cloud apps through the Workbench web UI.



Introduction

From the Workbench web UI, users can execute a number of operations on cloud apps.

This article focuses on basic app operations. It assumes that you have already opened a workspace in the Workbench web UI and navigated to the Apps tab.

List your cloud apps and check their status

Your apps are listed in the Apps tab of the workspace.

The Apps page for a
  workspace.
The Workbench Apps tab.

A badge in the top right corner of each app's card denotes its status, which can be one of the following:

  • Creating
  • Provisioning
  • Startup script
  • Starting
  • Running
  • Stopping
  • Stopped

For more information about the operations you can perform on apps that are either Stopped or Running, see Operations on existing apps. Apps that are in the process of Starting or Stopping cannot be operated on.

If you have an app that seems stuck on either Starting or Stopping, please contact the Support team for help.


Create a new cloud app

The steps below will walk you through creating a new JupyterLab Compute Engine app.

In the Apps tab of your workspace:

  1. Select + New app instance to open the Creating app dialog.

    A workspace's Apps page with no apps
created yet.

  2. Select an app type from the list. In the image below, JupyterLab is selected. Click Next.

    The Select app dialog, the
first step when creating a new app.

  3. On the Choose config step, you'll see a default configuration, as well as any other configurations used in previously created apps in the workspace. Select a configuration and click Next.

    The Choose configuration
dialog, the second step when creating a new app.

  4. Select the Workbench app image or enter a custom container. In the image below, the Workbench - R, PyTorch, TensorFlow (latest) image is selected.

    You can also change the machine type, which determines the number of CPUs and total memory available. You can also attach GPUs to the VM.

    In addition, you can change the data disk size for your app. The default recommended size is 500 GB for Compute Engine instances. However, it can range from 50 GB to 65,536 GB (64 TB). Please note that the data disk size can't currently be customized via the UI for Dataproc clusters.

    Finally, you can choose to have a running app automatically stop after a specified idle time. The autostop idle time is set to 4 hours by default, but it can range from 1 hour to 14 days. You can also opt out of the autostop feature.

    The Compute options
  dialog, the third step when creating a new app.

    To learn more about configuring the compute profile of your app, see Compute profile configuration options for GCP and AWS apps.

    Once you've finished customizing configurations, click Next.

  5. Enter a Workbench ID, instance name, and description (optional) and click Create app.

    The Review details dialog,
the last step when creating a new app.

Other app options

Other app options besides JupyterLab GCE instance include:

  • JupyterLab Spark cluster (Dataproc cluster)
  • R Analysis Environment
  • Visual Studio Code
  • JupyterLab (NVIDIA NeMo)
  • JupyterLab (NVIDIA Parabricks and CUDA-X Data Science)
  • Workbench AI
  • Custom

See Cloud app options for more details.


Operations on existing apps

Stop an app

When you create an app, it will automatically provision and start it. Its status will update to Running once it's ready to use.

To stop an app that's currently running, select the Stop button. This will immediately send the instruction to stop the app; there is no confirmation step. However, there may be a lag of a few seconds before the status is updated in the Workbench web UI.

An app's details card,
  with the Stop button highlighted.
Stop a running app.

Stopping the app should take less than a minute. During that time, you cannot restart the app; you can only edit its name and description, or delete it.

If your app has autostop enabled, you'll see the autostop idle time listed in the app's card. You can still manually stop the app any time before it’s set to automatically stop.

Start an app

To start an app that is currently stopped, select the Start button. This will immediately send the instruction to start the app; there is no confirmation step. However, there may be a lag of a few seconds before the status is updated in the Workbench web UI.

Starting the app should take less than a minute. During that time, you cannot stop the app; you can only edit its name and description, or delete it.

Edit an app

You can edit the ID, description, and autostop idle time of your app at any time. Your app's compute profile can be updated only when the app is stopped.

Select Edit in the three-dot action menu of the app card. This will bring up the Editing dialog. Edit the fields as desired. For compute profile changes, you can see cost estimates update in real-time. Select Update to save your changes.

An app's details card, with
  the Edit button highlighted.
Edit an app's configurations.

Delete an app

You can delete an app by selecting Delete in the three-dot action menu of the app card.

An app's details card,
  with the Delete option highlighted.
Delete an app.

This will bring up a deletion dialog. To proceed, check the box confirming your intent to delete the app and its associated resources, then click Delete app.

The Delete app dialog.
The app deletion dialog.

Other ways to modify your app's compute profile

You can also modify an existing GCP app's compute profile through the Google Cloud console or via the Workbench CLI (command-line interface), using the wb resource update gcp-notebook command. For both options, the app needs to be Stopped first, as described in Stop an app.

For details on updating your GCP app via the Cloud console, see Manage your apps in Google Cloud console.

To learn more about the available cloud compute options, see Compute profile configuration options for GCP and AWS.

What happens to apps when a user loses write access

Cloud apps are private to the user who created them. Because running an app requires write access to the workspace, Workbench automatically cleans up a user's apps when that user loses write access — for example, when a workspace owner downgrades a collaborator from Writer to Reader, or removes them from the workspace.

When a user loses write access to a workspace:

  • The user's write access to their apps is revoked, and each affected app is marked as abandoned.
  • Any running app instances are stopped.

Restore access to abandoned apps

If a user's write access was removed by mistake, a workspace owner can simply re-grant the user the Writer (or Owner) role. When this happens, Workbench automatically restores the user's access to their previously abandoned apps.

Delete abandoned apps with the CLI

If a collaborator has left the workspace for good, a workspace owner may want to find and delete the apps that collaborator left behind. Because owners can manage apps created by any user in the workspace, you can discover abandoned apps using the Workbench CLI (command-line interface).

Use wb app list to see all apps in the workspace. To list only the abandoned apps in the current workspace:

wb app list --abandoned

You can also filter apps by owner email:

wb app list --owner=<email>

To see full details for a single app, including its owner and ownership state, use:

wb app describe --id=<app-id>

As a workspace owner, you can delete the abandoned apps that are no longer needed. Deleting an app also deletes its data disk. All data stored on the app's local storage disk will be lost.

To delete an app from the Workbench CLI, use its ID:

wb app delete --id=<app-id>

Next steps

See Overview of cloud app types for more details about the types of cloud apps available on Workbench and how to use them.

Last Modified: 2 September 2026