Hey again, back with another question... When using the

supertokens-website

package with fetch interceptors active, if I make a request against an express backend that's configured with

supertokens-node

using the

Session

recipe and both the

Session.verifySession({ sessionRequired: false })

and

supertokens.errorHandler()

middleware(s) for a given route, I (when applicable) get back a

401

from the server with a message "try refresh token". At this point however, nothing happens in the front-end. Should the fetch interceptor be auto-trying to refresh the token here or is this something I need to manually handle?