We've already fixed this in the new version. The bug occurred because you entered the location with two quests that both required visiting it. Try loading an earlier save (check autosaves) where only one quest was active—that should resolve the issue.