This issue came out alongside patch 1.19. It's been already reported a few times as you can read HERE, HERE, and HERE, so it's currently being investigated.