Yandex Cloud
Search
Contact UsTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • AI for business
    • Security
    • DevOps tools
    • Serverless
    • Monitoring & Resources
  • 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
    • Price calculator
    • Pricing plans
  • Customer Stories
  • Documentation
  • Blog
© 2025 Direct Cursus Technology L.L.C.
All solutions
    • All solutions for DataSphere
    • Resolving project startup errors in DataSphere
    • Resolving the `Failed to deserialize variable` error
    • `Table of Contents` extension is missing in the JupyterLab extension catalog
    • Getting access to GPU g1.1 and higher configurations in DataSphere
    • Resolving issues with long code execution within DataSphere project cells
    • Resolving the `Servant not allocated` error when running code within DataSphere project cells
    • Resolving the `TestsFailure` error
    • Resolving the `Token authentication is enabled` error
    • Resolving errors with project access or login
    • Resolving the `KernelNotResponding The kernel died unexpectedly` error
    • Fixing the `ConnectTimeoutError` error when installing packages through pip
    • Resolving the `Device or resource busy` error

In this article:

  • Issue description
  • Solution
  • If the issue persists
  1. DataSphere
  2. Resolving the `Failed to deserialize variable` error

Fixing the Failed to deserialize variable error

Written by
Yandex Cloud
Updated at December 17, 2025
  • Issue description
  • Solution
  • If the issue persists

Issue descriptionIssue description

When you open a DataSphere project, you see the following error message:

Failed to deserialize variable %VAR_NAME%
Run the following code to delete it: del_datasphere_variables

Where %VAR_NAME% is the name of the variable the system was unable to deserialize.

SolutionSolution

The following variables cannot be serialized means that some variables cannot be serialized and saved. The interpreter keeps its current state when the configuration changes. All computation results, including variable values, are also saved.

Note

Since some variables cannot get serialized, they cannot be saved. For example, let's assume there is a variable with a file open for writing: f = open("file.txt", "w"). You will see the following warning when assigning values to such variables: The following variables cannot be serialized. Such a warning will not affect your code execution and further computation results.

Run the following code to delete it: del_datasphere_variables means that the variable previously resided in GPU memory but was not moved to the current CPU memory.

The error message suggests how to reset the variable: use the del_datasphere_variables method to delete it, and then run all associated cells in the same configuration.

If the issue persistsIf the issue persists

If the above actions did not help, create a support ticket. Provide the following information in your ticket:

  1. Project URL from the browser address bar.
  2. Full text of the error message.
  3. HAR file with the recorded communications between the browser and the server hosting the DataSphere project.

Was the article helpful?

Previous
Resolving project startup errors in DataSphere
Next
`Table of Contents` extension is missing in the JupyterLab extension catalog
© 2025 Direct Cursus Technology L.L.C.