Notebook could not be saved error

%3CLINGO-SUB%20id%3D%22lingo-sub-2793926%22%20slang%3D%22en-US%22%3ENotebook%20could%20not%20be%20saved%20error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2793926%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%3C%2FP%3E%3CP%3EI%20am%20using%20Azure%20Lighthouse%20to%20access%20one%20of%20the%20client%20environment.%20Everything%20is%20working%20fine%2C%20I%20have%20contributor%20privileges%20on%20the%20customer%20tenant.%20When%20I%20try%20to%20Clone%20the%20notebook%20by%20saving%20it%2C%20it%20gives%20the%20error%20%22Notebook%20could%20not%20be%20saved%22.%20Any%20thoughts%20how%20to%20fix%20it%3F%3F%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22FahadAhmed_0-1632888480231.png%22%20style%3D%22width%3A%20276px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F313494iF2CE1F2A95F68A06%2Fimage-dimensions%2F276x500%3Fv%3Dv2%22%20width%3D%22276%22%20height%3D%22500%22%20role%3D%22button%22%20title%3D%22FahadAhmed_0-1632888480231.png%22%20alt%3D%22FahadAhmed_0-1632888480231.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3EThanks%3C%2FP%3E%3CP%3EFahad%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

Hello,

I am using Azure Lighthouse to access one of the client environment. Everything is working fine, I have contributor privileges on the customer tenant. When I try to Clone the notebook by saving it, it gives the error "Notebook could not be saved". Any thoughts how to fix it???

 

FahadAhmed_0-1632888480231.png

Thanks

Fahad

2 Replies
Hi - I had the exact same issue - and was correctly pointed to it being a browser issue - first of all try and do the same in an alternative browser - and then use the same broswer and reset the cookies status - as that is where the problem lay .... cookies and saving ....

@wootts I saw your thread for the same and also applied the cookie and cache reset however it didnt solve the issue. Please note that since I am using Azure Lighthouse so the scenario would be different in this case.