It’s addressed in the patchnote for the upcoming Session 2. You just need to endure another 20 days for this known and internally fixed issue to hit official.