Error on moment - After finish of breakthrough into next match no auto sear

[Flapple824]

@EA_Atic 
@d6qfzpr645dq 

same topic --> search for  " Error 3:2907 J:2903J P:84955732 "

@EA_Atic repair doesn´t fix this error  - for me 

[1Atma]

@EA_Atic

Yes, happened several times today. I can go to conquest and cancel it when I join, go back to breakthrough and it works. I've seen posts on reddit with the same problem.

[Styrophone1]

Possible workaround!!! 

Guys i've been having the same issue, but it seems to work if you que up for another gamemode for a couple of seconds and then cancel, before queing up for breaktrough. Works so far for me. 

[RepanMike]

@EA_Atic Yeah its back now for me. Worked fine for whole day but now back again 😭

[BaldHalfwimsy]

I was just playing BF2042 last night, and now I can't connect at all. It tries to connect to online services and then I get Error Code 15:1305P:1302P:1300P:1301P:-7A. 
I play via Steam on PC if that helps. 

[Styrophone1]

@NoAIM-ToT Like this guy said

[NoSurprises97]

Just started getting the exact same issue, any fixes yet?

[EA_Cath]

Hey everyone, thank you for your reports! We have raised the matchmaking issues to the teams for investigation. We will let you know if we have more info to communicate.

Thank you for your patience!

edit: Just a little update people, could you provide the following information? That would be a great help for the investigating teams:

1. Region:

• US, East Coast/West Coast?
• EU, East, West?
• Asia, where in Asia?

2. Platform

3. Which Breakthrough did you queue for?

Many thanks!

[junkPost]

It happened now after the second round! First Kaleidoscope, error after second round:Nordvik

1. Region:

EU, Germany

2. Platform

PC

3. Which Breakthrough did you queue for?

normal Breakthrough

[eBraunsWorld]

Matchingmaking errors occur after playing 3 - 5 rounds of breakthrough. In-game chat reveals I am not the only one with this issue.

I've tried restarting the game, repairing the game via Origin, redownloading, clearing cache, updating drivers, and restarting computer. None of this has fixed the issue.