This issue was not happening as we did a redesign of CA Clarity and it is no longer using the same tools when rendering the webpage. This is why the issue did not exist in Clarity 12. It started occurring in release 13.
Try the following changes, they helped several customers:
1- Apache Reverse Proxy Change:
smproxy.conf - set KeepAliveTimeout to 30 seconds (I believe the default was 5)
2- On the F5, modify the One Connect Profile and set it to reuse TCP connections (Connection pooling) with your system administrators. We need F5 not to close those connections and to allow new requests to re-use the existing TCP connections
- Make PPM timeout (in System Settings) smaller than the SSO timeout.
Please let me know how it goes.
Thank you -Nika