Applicability

When you upgrade Allure TestOps from version N to version M, there might be some consequences:

• Application has 2 components – Backend (the server part, BE) and Frontend (the part you see in the web-browser, FE). 
• FE uses API calls to communicate with the BE.
• When you upgrade an application that has client-server architecture, the BE always has new binary files, new logic and new/updated API. 
• FE code is stored on server side and is cached on the end user browser side, and this caching can generate issues when you upgrade a client-server app.
• When you have cached FE code after an upgrade, it might use old API calls to new BE, that does not operate with the API calls used by cached (i.e. old) FE.
• As a result, the application can throw 401, 403, 405, 409 messages and won't do what it is expected to do.

Solution

So, for the normal work, after upgrade (does not matter whether you are using on-premises deployment or SaaS), you need to clean the FE cache, so your browser will be forced to download FE components from the server side.

How to clean the cache

1. Open developer tools of your browser
2. Proceed to Application tab
3. Select Storage in the left menu
4. In the right side of the selected item you will see the button "Clear site data", click it.
5. Then refresh the page while holding "Shift" key on the keyboard.