Bug #1300

Post-Matchmaking Deep Dive and Assignment State Desync Issue

Status:	Open
Priority:	High
Added by:	atomsift26 on April 14, '26
Assigned to:	Unassigned
Due date:
Reported for:	S06.04 Auto

Steps to Reproduce

1. Load a known stable save state (pre-issue / clean baseline).
2. Confirm Deep Dive and assignment missions function normally in solo play.
3. Participate in a public matchmaking mission (either host or join).
4. Complete the mission and return to the hub.
5. Continue gameplay normally (no immediate visible issue).
6. Start or attempt a Deep Dive or assignment mission afterward.
7. Observe that Deep Dive behavior becomes inconsistent and/or assignment validation no longer behaves correctly in public sessions.
8. Note that solo assignment missions may still function correctly, but the state persists across sessions until reverting to an earlier save.

Explanation

I think I’ve identified a systemic state desync affecting Deep Dive and assignment validation after public matchmaking. It appears to cause persistent regression/desync behavior in subsequent solo and public sessions. Has this type of behavior (assignment / Deep Dive state desync after public matchmaking) been seen or addressed in any previous patches or known issues? If not, I can continue gathering controlled reproduction steps and additional timestamps to help isolate it. I have further info if needed.

Watchers

Watch