Hey there.
Take a look at this thread:
It should be fixed in SonarQube v10.2, scheduled for release this week.