had an interesting and concerning issue yesterday. a user logged into our application with google auth and the supertokens react frontend started calling the

/auth/user/email/verify

endpoint multiple times a second (which I think it shouldn't call in the first place, there's only email verification for emailpassword users). checking our frontend analytics it looks like they were just using the app normally while the react SDK continued to call this endpoint in the background, so I don't think there's any foul play here. checking our backend and the supertokens-core logs it looks like it was stuck in some sort of loop trying to regenerate the sessions and verify the email. the supertokens service was brought pretty much to a halt until it finally recovered (seems like the cronjobs ended it?). has anyone seen this before or have any ideas as to what happened and what we can do to prevent it? attached is an example of the logs, you can see the service getting hammered. there was about ~34,000 api calls to the supertokens service over the course of a few minutes. let me know if you need any more information, would be great to know what could have happened so it can be prevented for us and other users in the future!