Cache Clear Required after each release or upgrade
search cancel

Cache Clear Required after each release or upgrade


Article ID: 269375


Updated On:


Clarity PPM SaaS Clarity PPM On Premise


Many users reporting issues while accessing MUX screens post upgrade, where the user while access MUX is rendered a blank screen followed by an error "Page could not be loaded". The user is forced to clear the cache to overcome this and doesn't provides a pleasant user experience.

Steps to Reproduce: 

  • Use clarity in any of prior version let say 16.1.1
  • Upgrade to 16.1.2
  • Login back to MUX post upgrade 

Expected Results: User should be able to login to MUX 

Actual Results: MUX throws different errors until the browser cache is cleared 


Release : 16.1.2, 16.1.3


Index.html file under Clarity_home\tomcat-app-deploy\webapps\pm is cached and due to that client side static files are loaded causing mismatch of cache from server side 


DE70714, will be addressed in release 16.2.0, but you will not see the benefit until the rollout of 16.2.1, henceforth you will have to potentially clear caches one more time once 16.2.0 is in place.


  • Clear the browser cache