Databricks kicking me out every 2 minutes

[sminamioka]

After the session expire every 2 minutes as show below, I can't log in afterwards as shown further below. 

What the heck is this? Then I have to wait the platform own will to allow me to log in many minutes later.

[Ashwin_DSA]

Hi @sminamioka,

As far as I can tell, there are currently no known issues or incidents. Are you experiencing this issue with the Databricks Free Edition or with a paid Databricks instance?

Please feel free to try the steps below to rule out any isolated issues...

1. Try a different browser or incognito mode

2. If possible, test on another physical machine and a different network.

3. If you are, please disconnect it temporarily to see if that resolves the issue. If it works on other machines and networks but not on your corporate device or network, it's likely that the corporate proxy or security software is interfering with cookies or Single Sign-On (SSO).

4. Log out of any active Azure portal sessions, such as login.microsoft.online.com and *.azuredatabricks.net, and then close all browser windows. After that, you can go directly to the workspace URL and sign in from there. This may help resolve the issue.

5. If you have a workspace administrator, check to ensure that you are listed as an active user and not marked as inactive, as this could sometimes cause problems.

If none of these solutions work, the best course of action is to raise a support ticket with the relevant details, as the community cannot address this issue directly.

Let me know how it goes...

If this answer resolves your question, could you mark it as “Accept as Solution”? That helps other users quickly find the correct fix.

[CynAuad]

Hi! I've been having the same problem since Sunday.
I've tried every possible solution: incognito mode, clearing cookies, different WiFi network, Google DNS, different user account — issue persists on all attempts.

[CynAuad]

@Ashwin_DSA  I see there was a similar issue in 2024. https://community.databricks.com/t5/get-started-discussions/session-expired-error-databricks-communi...

[Ashwin_DSA]

@CynAuad ,

Are you facing the issue in free edition or paid?

[sminamioka]

I'm using Azure Databricks Premium. I've tried between 3 different computers and browsers, it's so rediculous this problem. How is possible a multi billion company with a stupid problem like this?

[CynAuad]

Hi @Ashwin_DSA! thanks for your repley!

In the free version. I still have credits for a few more days. I didn't have any problems for almost 15 days, but the issue started 4 or 5 days ago and has been happening constantly ever since.

[CynAuad]

This is aindividual account with free credit (first time) to use on Databricks Premium.

[Ashwin_DSA]

Because you’re on a paid Premium workspace, the next step really needs to be a support investigation so someone can look at logs, which we can’t do from the community side. If you can, please open a Databricks Support ticket (or ask your admin to) with:

• Your workspace URL and region
• Your user email
• 3 - 4 exact timestamps (with timezone) when you got logged out

If this answer resolves your question, could you mark it as “Accept as Solution”? That helps other users quickly find the correct fix.

[Kowsi]

I upgraded to premium and still face this issue

[sminamioka]

how can I raise a ticket to them?

[learnawscloud]

Getting same error today, happened multiple times. If you try to login immediately, it throws error same as yours. You have to wait for some time, and it lets you login after couple of hits. Highly frustrating.

Error details:

"""

Sign in

Sorry, but we’re having trouble signing you in.

AADSTS90015: Requested query string is too long.

Troubleshooting details

If you contact your administrator, send this info to them.

Request Id: 2dd8b625-0d34-435b-bf69-c89bc1db5800

Correlation Id: 725ac6b7-6eb7-44ae-b08d-bbc32f1f8ad8

Timestamp: 2026-03-23T12:44:49Z

Message: AADSTS90015: Requested query string is too long.

Flag sign-in errors for review:

If you plan on getting help for this problem, enable flagging and try to reproduce the error within 20 minutes. Flagged events make diagnostics available and are raised to admin attention.

"""

[sminamioka]

So garbage this error, seriously.

[learnawscloud]

Breaking all rhythm. Hands-on that I can finish in 15 mins, is taking more than an hour. Almost zero productivity, wasted money.

[CynAuad]

I couldn't create the ticket—I don't have a way to do it, either through Databricks or Azure.
With all the complaints I've seen this week, I find it hard to understand why they haven't fixed the error. I'm sure they can detect it.