[July 2019]
We’re still seeing this happening on 9.5.13 clients. It’s gotten quite tedious, and I’m close to putting in policy actions to deal with the customer areas that are easy to identify. (Lame but whatchugonnado)
Any news on isolating the cause, and hopefully a permanent fix?
-Andrew