It will be fixed with the next patch. No ETA on its release as of yet but we’ll let you all know once we have anything else to share.
Since the original issue has been acknowledged and fixed internally we’ll proceed to close the thread. Please keep an eye out for further announcements on patch releases.
Thanks.