Escape from Tarkov "profile data not saved" error (fix)
Written by
Last checked
September 23, 2026
After extracting or ending a raid, a dialog reads "Some error occurred on the backend, profile data could not be saved" — and the loot or progress from that raid doesn't show up afterward.
Also appears as: profile data could not be saved, some error occurred on the backend profile data could not be saved, tarkov lost loot after extract, escape from tarkov extract but lost items
This message is the specific, worse variant of Battlestate's backend error 1000: it fires when the server accepts your extraction but then fails to write the resulting profile changes, so the loot and progress from that raid are lost even though you got out alive. A 21-reply Steam Discussions thread on exactly this symptom, and a second thread that names the "1000 - Backend error" explicitly, both describe the same sequence — a clean extract followed by a save failure — with reports clustering around high-server-load periods the same way error 1000 does generally. There's no confirmed way to recover a specific lost raid's items; the fixes below are about reducing how often it happens, not restoring what's already gone.
No problems reported in the last 15 minutes.
Is Escape from Tarkov down right now? Live reports →What to try
- 01Reported
Check the status page and @tarkov for high-load windows
Check status.escapefromtarkov.com and the @tarkov account before assuming anything can be done locally — reports of this exact message cluster around the same high-load windows (wipes, big patches, launch-week traffic) as backend error 1000 generally.
- 02Unconfirmed
Wait a few minutes on the raid summary screen after extracting
Wait a few minutes after extracting before backing out of the raid summary screen or starting another raid — several reports describe this save failure hitting players who exit quickly, though it's not confirmed to be the actual cause rather than coincidence.
- 03Unconfirmed
File a bug report through the BSG Launcher with your session log
File a bug report through the BSG Launcher with your session log and the approximate raid time — this is the only channel Battlestate has for a lost-loot claim, and there's no guarantee of restored items.
Did this fix it for you?
Your answer helps the next player know whether these steps are worth trying first.
Hit this error? Leave a comment
Say where you are, what you see on screen, and whether any fix worked for you.
No links. Anonymous, no account. Keep it about the game.
What people are saying
Notes from players who've hit this one — no time limit, an answer from months ago is still an answer.
- Nothing reported here yet.
From isthisgamedownMatched on ""
From isthisgamedownMatched on ""
From isthisgamedownMatched on ""
Other Escape from Tarkov error codes
Recently added
- AION 2 "insufficient gameplay record" market listing block
- ARC Raiders error ARMR0014 on Storms and Night Raids
- Enshrouded server exits 0xC0000135 on Windows Server Core (fix)
- Gears of War: E-Day stuck on "Fetching Data" (fix)
- Gears of War: E-Day lucas-gnasher: reward expired
- Gears of War: E-Day reaver-tyrus: can't queue ranked
- Valheim server "App 896660 state is 0x6" after update (fix)
- Valheim Unity crash error (0xc0000005): what to try