It’s likely a similar case to the one described in this thread.
This issue has been resolved in SonarQube 10.5.