Hey there.
What CI are you using to execute the analysis (Jenkins, something else…)
Probably, the SCM revision that’s being calculated in the background (sonar.scm.revision) starting with 69f48c doesn’t exist in the repository where the pull request has been raised. There are a few reasons this can happen: but I recommend checking first, where does the 69f48c exist? In the forked repo, a merge commit created by your CI (Jenkins commonly does this), somewhere else?