We're using NodeJS supertokens SDK + managed service in production and as of today all backend verifySession() middleware calls are returning 401. Is something wrong with the managed service?

We're using NodeJS supertokens SDK + managed service in production and as of today all backend verifySession() middleware calls are returning 401. Is something wrong with the managed service?

I'd upgraded to 9.1.1 with a deployment today

Really strange

const { verifySession } = require('supertokens-node/recipe/session/framework/express') const EmailPassword = require('supertokens-node/recipe/emailpassword')

What does sign in return?

odd

Reallly strange

yeah, I didn't even revert anything

If it happens again, please do capture the following:

Ok, was able to reproduce this morning

alright! Tell me more please.

This is in localhost - not on production - but same situation seems to apply

Right. I see.

The 401 is of course because the cookie is missing

Do you use axios or fetch?

Axios

Added supertokens' interceptors to add axios instances?

yep! Flow works in general

no need to switch. Should work well with axios as well.

this only seems to happen in our application when you have multiple tabs / windows open and you log into different user accounts

from the request headers, it seems that the interceptor was not applied

I was testing across a couple different organizations when the reproducer occurred

are you querying an API that is != to the apiDomain value in supertokens.init?

nope, that doesn't ever change

huh.. can we get on a quick call to debug this?

sure!

cool! lmk

the issue is "fixed" when I kill my browser window

i see. Lmk if you would like to hop on a call

OK! I figured it out

ok awesome!! :))