Hi @dmptiprabhakar,
I have seen a few cases like this recently after the transition from Community Edition to Free Edition, and there are actually two different things happening here that are often mixed together.
First, about the notebooks:
Community Edition was never designed with strong persistence guarantees, and during the transition to Free Edition, Databricks did not perform a full workspace migration. In practice, that means most CE workspaces were not carried over, so notebooks are typically not recoverable unless they were exported beforehand.
Second, about the login error:
From what you described, this does not look like a simple browser issue. It is more likely an account state mismatch between the legacy Community Edition identity and the new Free Edition account system.
Free Edition is tied to the newer Databricks account model, and I have seen situations where:
- the same email exists in different accounts
- the user is partially registered in the new system
- the workspace is not fully provisioned after first login
A few things you can try:
1. Force a clean authentication flow
Use an incognito window and log in directly via:
https://accounts.databricks.com
2. Avoid reusing the same session path
Do not use bookmarked Community Edition URLs, start from the Free Edition entry point instead
3. Validate if it is account-specific
Try creating a new Free Edition account with a different email
If that works, it strongly indicates your original account is in an inconsistent state
At that point, there is no real workaround on the user side.
This needs to be fixed by Databricks support, because it is tied to account provisioning.
Suggestion going forward:
If you plan to continue using Free Edition for experimentation, I strongly recommend exporting notebooks or backing them up to Git. CE and Free Edition are both best treated as non-durable environments.
Hope this gives you a clearer direction ๐