View Single Post
This was fixed in 4.0.2, released on Feb 6th. If you are still seeing this behavior please contact support.