Hey Pr3daToR, there's a dedicated thread HERE about this issue.
We previously implemented changes in an effort to correct this, so it's really disappointing to see it's presented itself again. If you haven't already, please take a moment to share your feedback in the above discussion using our Bug Report Template.
Comments
We previously implemented changes in an effort to correct this, so it's really disappointing to see it's presented itself again. If you haven't already, please take a moment to share your feedback in the above discussion using our Bug Report Template.
Thank you very much in advance for your help!