We have some areas of our frontend that are accessed by anonymous users…. But since supertokens is initialised it’s just spams the refresh api route constantly. Is there a way to turn it off, or only call refresh when logged in?

Hey! So the problem is that it calls the refresh endpoint many times per user or once for each new user?

User is not logged in, and hasn’t yet been asked to login

It should call the refresh just once per new user then. Do you find it calling it multiple times?

Its an anonymous route…. But the page has been open a couple of minutes and so far browser has spammed the refresh endpoint about 2000 times

Huh.. so there could be another issue then

So this is a page before the user is asked to login…. So it’s anonymous

Aftwr a refresh is called, I assume you get a 401?

I think its getting a 200 but it’s not logged in so I don’t know why it’s even calling refresh

Well. The SDK called refresh if there are no cookies at all that are set. To check it a session exists or not

May have been logged in before and not logged out I guess

But then it shouldn’t be calling refresh continuously