does anyone have any idea about it?

I don't know what's happening but you could customise that error page so that it redirects the user to the homepage (or login) IF they are in the checkout AND they are logged out.

After doing more testing, I am not able to move/load any other page, I just get a blank page and in the network it states the same issue:

Sorry, I'm not aware of any mechanism that deletes cookies after a timeout

Oh, I see, I thought it was the root since after I delete them I am able to see the site normally, I will continue troubleshooting it. this is happening in production (staging site) but we did not have this issue in SB (only the minor version of SCA is different). I am not sure if there is any setting to handle the session or something like that, I just checked the touchpoints and they are setup correctly.

OK, I'm a bit confused because this sort of thing shouldn't happen. I don't understand how a user can have 'insufficient permissions' to a view the login page. What exactly is happening before this happens?

Yeah, I agree with you, this is how I am reproducing the issue: 1 - login (redirects to my account as usual) 2 - do nothing and wait until session expires (15 mins) 3 - click to another page on the site or reload the site (I got redirecting to the login page but with the 403 error or sometimes just a blank page)

Is it a full page error is does it in the appear in the 'content area' of the page? Because the latter, I believe, is considered 'normal' unfortunately. That can occur when your user makes a call to a service but they are logged out, and that is the message the service returns (but the application hasn't changed state so it doesn't perform a redirect)

No, this is not a full page error, the header menu is loaded and other parts of the site, the error is displayed just in a area of the page and whenever I try to go to another page then I got the blank page. This is pretty weird

OK then what I said applies

Yeah, I agree the permission error is completely normal but then It means the application is recognizing as a 'logged user' and try to make a call which is not allowed, probably one of the methods is failing to identify correctly the user

Yes, there should probably be a check before the call is made to see if the user is logged in; OR once the error is returned, they are redirected to the login page before they see the error.

I will try to see what is going on if not we will probably open a case since it also happens when I use the source code of the site so none of our extensions is impacting this. Thanks for your time @Steve Goldberg!

@eminero Did you have any luck with this? I'm seeing it when testing in production as well. Thanks!

I do not even remember what this issue was but I am glad you fixed it!