Currently, when a request to user/sessions/<token>/refresh fails, the Editor is presented with the login screen. This request is performed by Platform UI on a number of different occasions, including navigating through the Content. However often the Editor is still logged in despite that fact that "refresh" request failed - the failing request only means that the session was not refreshed, but it still might (and in most cases is) active. Therefore the Editor should be able to continue working despite errors on "refresh" requests - the errors should be invisible to him.

Steps to reproduce

1. Create new eZ Platform installation.
2. Login to the Platform UI.
3. Make the user/sessions/<token>/refresh requests fail. This can be done for example by adding the following line as the body of the function refreshSessionAction inside the file vendor\ezsystems\ezpublish-kernel\eZ\Publish\Core\REST\Server\Controller\SessionController.php:

   throw new \Exception();
   

4. Navigate to "Content" - > "Content structure". You will see the login form. However, you should still be able to see the contents of "Content" - > "Content structure" tab, because your session is still valid.