Yandex Cloud
Search
Contact UsGet started
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • AI for business
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
© 2025 Direct Cursus Technology L.L.C.
Yandex DataSphere
  • Getting started
    • All guides
      • Creating a project
      • Adding a user to a project
      • Managing project labels
      • Selecting a Python version
      • Resizing project storage
      • Changing project settings
      • Setting project limits
      • Deleting a notebook or a project
      • Removing a user from a project
      • Using a shared resource
      • Troubleshooting
    • Migrating a workflow to a new version
  • Terraform reference
  • Audit Trails events
  • Access management
  • Pricing policy
  • Public materials
  • Release notes
  1. Step-by-step guides
  2. Project management
  3. Troubleshooting

Troubleshooting

Written by
Yandex Cloud
Updated at August 15, 2025

Errors occurring in DataSphere projects may require you to reset the installed packages and computations or change your project settings. For most of these tasks, you will need the datasphere.community-projects.developer role or higher. To resize the project storage, you need the datasphere.community-projects.editor role or higher.

If you are having project access issues, try these steps:

  1. Select the project in your community or on the DataSphere home page in the Recent projects tab.

  2. Click More.
  3. Click Troubleshooting in the list that opens and select the required action:
    • Factory reset: Resetting the interpreter state and deleting all installed libraries. This will not affect your notebook codes, cell outputs, and all project resources. This option can be helpful in case of invalid libraries or full storage.
    • Reset JupyterLab workspace: Closing all open files and notebooks. Corrupted files and notebooks may prevent JupyterLab from working properly.
    • Clear output: Clearing all cell outputs of open notebooks. Excessive cell output may negatively impact JupyterLab performance and slow down your browser.
    • Change project storage size: Resizing the project storage. The project will be stopped. This will fix the errors caused by full storage.
    • Stop JupyterLab and VM: Stopping all computations, closing open notebooks, and shutting down the VM. This can be helpful when the project gets stuck for unknown reasons, or if you need to stop running calculations.

Was the article helpful?

Previous
Using a shared resource
Next
Connecting to JupyterLab from a local IDE
© 2025 Direct Cursus Technology L.L.C.