This was resolved with a client update (build 42940) as of Tuesday March 29th. Have you still been experiencing this behavior since then? If so could you provide a date and time for when this occurred?
2 Likes