Invisible merge request thread

Summary

Merge request threads are sometimes invisible in the GitLab UI, despite being accessible via the API. This appears to be related to force pushes and automated thread creation via API.

Steps to reproduce

Note: Unable to reproduce manually - this occurs intermittently with automated processes.

1. Create a merge request with commits
2. Use automation to create diff comments/threads via GitLab API
3. Perform a force push on the merge request branch
4. View the merge request in the GitLab UI

What is the current bug behavior?

• Merge request threads are completely invisible in the GitLab UI. It shows user started thread, but I can't see any "reply"
• Threads are still accessible and visible via the GitLab API
• Browser console shows JavaScript error: Cannot read properties of 'null' (reading 'replaced_file'), from diff_with_note.vue
• The issue occurs intermittently with automated workflows that create threads via API

What is the expected correct behavior?

• All merge request threads should be visible in the GitLab UI
• Threads created via API should display properly in the web interface
• No JavaScript errors should occur when viewing merge request threads

Relevant logs and/or screenshots

Position from API

"position":{
            "base_sha":"9deb3f692f886807b7eefebeac3bc21cc97f576d",
            "start_sha":"826530e080333ae6188cb265146b43b2adf5554e",
            "head_sha":"79e59d8ba3fb736d4f833e76bd406190ea3be335",
            "old_path":"file.py",
            "new_path":"file.py",
            "position_type":"text",
            "old_line":null,
            "new_line":71,
            "line_range":null
         },

Gitlab Version: 17.11