Was this reintroduced in 2.1.3?
We upgraded to 2.1.3 last week, and have started seeing this since. If I downgrade to 2.0.5, the problem disappears.
Was this reintroduced in 2.1.3?
We upgraded to 2.1.3 last week, and have started seeing this since. If I downgrade to 2.0.5, the problem disappears.