Using !user.email_verified

In the HAR file capture we see there is a 404 when reaching out to /user/sso but this expected as discussed deeply here in this thread. However there doesn’t seem to be anything additional of note from the capture relating to your issue. I am still investigating what may be occurring and will share what I find :+1: