Hi I'm struggling to find an answer to a random (or seemingly random) issue.

Every now and again when our application tries to get a new token from the /api/jwt/refresh endpoint it is returning 400. The refresh token lifetime is set for 43200 mins, JWT lifetime is 300 seconds.

I can't seem to find a forced situation that I can replicate this. Have tried

• Getting a token, waiting a couple of days and then refreshing
• Getting token from one computer, then getting a new token from another and then refreshing from the first.
• Mixing the above two things

The one example I'm looking at in our dev env the token is for a user that hasn't been disabled etc in any way, the JWT had expire c2hrs before hand.

Any advice on how to debug this or a potential solution would be amazing

@abdoulaye-sow I'm seeing this in the /api/passwordless/start endpoint. The weird thing for us is that even though this is our Dev instance, we have no more than 5 concurrent users at the moment so we certainly shouldn't be overloading the system.

I'm starting to look into this now, but if you did find anything out I'd love to hear from you