I've experienced the same UI in your second screenshot yesterday when i was in the train with a very spotty internet connection. This looks like the skin style-sheet was not loaded properly. Do you get the same screen all the time? Do all users get the same distorted screen ?
What Pega version are you using ? A customer using Pega 7.1.6 with Tomcat for Pega server and Apache for load balancing experienced a similar issue. The issue was temporarily fixed by clearing the cookies from the web browser’s cache. The issue was patched in 717.
You will need HFix-21764 if you are on PRPC 7.1.7. If you are on another earlier version you will have to request a port of this fix. This is a really simple fix as well.
This fix resolves an issue with multiple Pega-RULES cookies being added to requests when using a load balancer, proxy, Cisco F5 etc. There was code incorrectly storing a Pega-RULES cookie at the browser cache level when header names were being modified by traffic components. When you logoff and log back in the file cookie would start to be used after it matched a specific URL. Then you ended up having two Pega-RULES cookies being set with each request to PRPC, one the old requestor value and one the current one. The issue starts to occur when PRPC server reads the old cookie value to static content request.
We use SESSION cookies, not browser level cookies, so this was causing problems. It's also why clearing cookies from the web browser's cache can resolve the problem, for a bit. You should never have to clear browser cookies with PRPC as we only ever should be using SESSION cookies. This has been corrected with this patch.
There is more information in SA-8960.
These types of screen distortions are 100% caused by this issue and is easily replicated with the correct setup. I can for instance replicate this issue in house using WebSEAL, which acts like a proxy server, very easily.
How did you do the Revalidate and Save? We are on 7.19 and have the same issue but i can't Revalidate and Save because the system will not give me the option of doing this with any Pega ruleset. I can only do it with my application rulesets.
Would you say this is something all PRPC 7.1.7 instances [which are using an F5] should have? (We have a couple...)
This thread seems to talk more about the screen distortions -- something I think I've seen -- but the Support Article focuses more on the cookies aspect only (while that may be the cause, there seems to be more to the "errors to be displayed" than reported)
Also, it sounds like Chris Koyl says this always happens -- is that true? That is, if I'm not seeing this regularly, I shouldn't be worried...