Hi @Coty
Have you encountered this issue since patch 3.0.1? The he issue should be fixed in that version.