[2023] KNOWN ISSUE: failed_found_no_lobby / Error Code: 3013

Due to an increase of players reporting failed_found_no_lobby / Error Code: 3013, I have chosen to merge all related posts here. This makes it easier for our Backend Engineers to parse multiple reports at once.

Work continues on this particular error, and I will post any relevant updates in the comments below. I will include links to any updates here.

For any new reports pertaining to this error, please help us out by including the information listed below in your report:

Issue Description:

Crash Report (If Applicable):
[Please see instructions on how to provide a crash report in the pinned Topic]

Steps to Reproduce:
[Please add the steps that can help our QA department in reproducing the issue. For example:]

1. Play Chasm Logistratum as Ogryn (Skullbreaker)
2. Attempt to pick up the second Grimoire
3. Observe Backend Error

Platform:
[Steam/Microsoft Store]

Player ID:
[Steam ID/Steam Profile URL/GamerTag]

Approx. Time of Issue & Timezone:
[MM/DD/YYYY, 00:00AM/PM] [TIMEZONE]

Upload Console Log:

1. Press the Windows key + R
2. Enter %appdata% within the search input and select ‘OK’
3. Navigate to AppData\Roaming\Fatshark\Darktide\console_logs
4. Locate the console log that corresponds with the session in which the issue occurred, by looking at the timestamps in the log names
5. Upload here

Similarly to Error Code: 2014, it does seem that 4G networks are more prone to this error.

Apologies for the time it’s taking to address this, I understand patience may be running low.