Can't find when it started, probably yesterday when we rolled out some updates, I will dig more into this and get back soon. I guess it's when we fetch from the API method that's using a different way to verify session