Unable to open ATE redirect error

This thread is resolved. Here is a description of the problem and solution.

Problem:
I can't get ATE to open. When I try to open the translation in ATE I am returned to my site with the following message in the URL: redirect_message=Our+session+has+expired%2C+please+log+in+again. I've tried unlogging and logging in to my site, it doesn't help.

Solution:
It was a problem with the chrome cache for your e.ate.wpml.com site. I was not helped by the advice in those tickets: clear cache with Ctrl+F5 or Ctrl+Shift+R. I was helped by clearing it via DevTools - Applications - Storage - Clear site data. However, the respective button had to be pressed during the second that your site was opened and immediately closed (with a redirect back to my site) when trying to open ATE. It certainly didn't work right the first time (otherwise I just cleared my site's cache, which wasn't necessary).

Relevant Documentation:

This is the technical support forum for WPML - the multilingual WordPress plugin.

Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.

Tagged: Exception

This topic contains 2 replies, has 2 voices.

Last updated by Lauren 6 months, 1 week ago.

Assisted by: Lauren.

Author	Posts
May 9, 2024 at 6:47 pm #15612100
olegA-5	I can't get ATE to open. When I try to open the translation in ATE I am returned to my site with the following message in the URL: redirect_message=Our+session+has+expired%2C+please+log+in+again. I've tried unlogging and logging in to my site, it doesn't help. Never in two years of using WPML has this ever happened.
May 10, 2024 at 2:43 pm #15615322
olegA-5	It was a problem with the chrome cache for your e.ate.wpml.com site. I found information about it by googling it. Since mid-April many of your customers have encountered this problem. Strange that the person in the support chat didn't tell me it could be it, considering how many tickets on this topic google brings up. In any case, I was not helped by the advice in those tickets: clear cache with Ctrl+F5 or Ctrl+Shift+R. I was helped by clearing it via DevTools - Applications - Storage - Clear site data. However, the respective button had to be pressed during the second that your site was opened and immediately closed (with a redirect back to my site) when trying to open ATE. It certainly didn't work right the first time (otherwise I just cleared my site's cache, which wasn't necessary).
May 10, 2024 at 7:17 pm #15616239
Lauren Supporter Languages: English (English ) Timezone: America/New_York (GMT-05:00)	Thanks so much for the update and details on what resolved it. The caching issue should have been resolved so this should no longer be happening, and in almost all previous cases, clearing the browser cache fixed the issue. Seems yours was slightly different and I appreciate the feedback in case we encounter any other similar tickets.