Need Help?

Search our documentation and community forum

Terra is a cloud-native platform for biomedical researchers to access data, run analysis tools, and collaborate.
Terra powers important scientific projects like FireCloud, AnVIL, and BioData Catalyst. Learn more.

Failed to check notebook status: "Autosave Failed!"

Comments

15 comments

  • Avatar
    Stephen Fleming

    Sometimes this state is accompanied by an issue with opening the Terminal.  Here's an example where it hangs forever with the message "Almost ready..."

     

    0
    Comment actions Permalink
  • Avatar
    Jason Cerrato

    Hi Stephen,

     

    We'll be happy to take a look! Can you provide the project name(s) and workspace(s) where you are seeing this happen? Is this happening on notebooks across different projects/workspaces, or in any one specific project/workspace?

    And please confirm that your user email is sfleming@broadinstitute.org.

     

    Many thanks,

    Jason

    0
    Comment actions Permalink
  • Avatar
    Stephen Fleming

    Hi Jason,

     

    Thanks!  It's bayer-pcl-single-cell/bayer_pcl_single_cell

    I have only ever used notebooks in Terra from within that particular workspace.  And yes, that's my email.

     

    Thanks!

    Stephen

     

    0
    Comment actions Permalink
  • Avatar
    Jason Cerrato

    Hi Stephen,

     

    To clarify, is the terminal open in a separate tab when this notebook error occurs?

     

    Kind regards,

    Jason

    0
    Comment actions Permalink
  • Avatar
    Stephen Fleming

    Hi Jason,

     

    The terminal message is not really well correlated with the notebook error.  Often the notebook error occurs without the terminal error.  The notebook error is the real problem for me, and it occurs much more often.  But the only times I've seen the terminal error (open in a separate tab at the same time) was when this notebook error was occurring, so I thought I'd just mention it in case there's some link.  But there might be no link.

     

    Thanks,

    Stephen

    0
    Comment actions Permalink
  • Avatar
    Andrew Blair

    Hello,

    I am also frequently running into this error when I use my custom Docker environment. In addition to the error posted above, I will receive a prompt to reload, cancel, or overwrite my notebook. No matter what option I choose, within seconds, I am re-prompted with the same question. Afterwards, I will receive the same autosave error. I notice this error recently started occurring when I create folders and then notebooks (in the folders) using the Jupyter GUI.

    Please let me know if there is any more information I can provide.

    Thanks,

    Andrew

    0
    Comment actions Permalink
  • Avatar
    Jason Cerrato

    Hi Stephen,

    We are still looking into this issue—thank you for your patience.

     

    Andrew, would you be able to share the project name(s) and workspace(s) where you are seeing this happen? And please confirm your email address.

     

    Many thanks,

    Jason

    0
    Comment actions Permalink
  • Avatar
    Jason Cerrato

    Hi Andrew,

    Are you still experiencing this error? w=Would you be able to share the project name(s) and workspace(s) where you are seeing this happen? And please confirm your email address for Terra.

    Kind regards,

    Jason

    0
    Comment actions Permalink
  • Avatar
    Andrew Blair

    Hi Jason,

    Yes, I am still experiencing this error. My email is andrew.blair@gladstone.ucsf.edu and the workspace is bruneauHeartHub-BRM. Thanks for your help!

    Best,

    Andrew

    0
    Comment actions Permalink
  • Avatar
    Jason Cerrato

    Hi Andrew,

    Can you provide the full workspace path, including the billing project?

    Many thanks,

    Jason

    0
    Comment actions Permalink
  • Avatar
    Jason Cerrato

    Hi Stephen,

    Our developers have released a fix that should improve the experience of the notebook. They suspect that memory issues caused these original errors, and recommend deleting and recreating the cluster in order to get the fix. While the fix doesn't prevent someone from using all the available memory in the kernel, it has the notebook failing more gracefully when this does happen so that you can retry your notebook commands.

    Please recreate the cluster and let us know if you experience any improvement in the notebook experience.

    Many thanks,

    Jason

    0
    Comment actions Permalink
  • Avatar
    Stephen Fleming

    Hi Jason,

    Just as a note, sometimes when I get that "Autosave Failed!" message, if I refresh the page, I get this:

     

     

    Don't know if that's any kind of a clue...

    I have not deleted and re-created my cluster, but I will try that eventually.  (Been putting it off because it's always hard for me to get a cluster set up the way I want it.)

     

    Thanks!

    Stephen

    0
    Comment actions Permalink
  • Avatar
    Jason Cerrato

    Hi Stephen,

    Do let us know when you have a chance to re-create it, and let us know how it goes! Many thanks for your help in reporting details of the issue.

    Jason

    0
    Comment actions Permalink
  • Avatar
    Stephen Fleming

    Hi Jason,

    One more note that may be helpful to others who read this...

    I have noticed very recently that some of the time when I get this error, my laptop has jumped onto a different wifi network (unexpectedly)!  If I go back to my main wifi network, the problem sometimes resolves.

    It may have been my own wifi connection issues the whole time... I'm still not 100% certain, but this is looking like a possibility.

    Thanks again for your help,
    Stephen

     

    0
    Comment actions Permalink
  • Avatar
    Jason Cerrato

    Hi Stephen,

    Thanks for letting us know! This type of thing can often happen if you have an unprotected network in your network history, especially if it's of higher priority than the protected network. It may be worth removing or lowering priority of the unprotected network to keep this from happening in the future—I'd recommend removing it completely if you don't really need to use it.

    Have you gotten a chance to recreate the cluster since the fix?

    Kind regards,

    Jason

    0
    Comment actions Permalink

Please sign in to leave a comment.

Powered by Zendesk