Lore/Revision Control broken on ALL projects after a crash — root cause found in logs

General Issues and Bug Reporting
, , , ,
1

Summary

Revision Control (Lore) fails to connect on all UEFN projects, including brand-new ones, after a crash occurred on one project. Client logs show the root cause is a corrupted data fragment that fails server-side decompression, surfaced to the user as a misleading “NotFound” error.

Please select what you are reporting on:

Unreal Editor for Fortnite

What Type of Bug are you experiencing?

Unreal Revision Control

Steps to Reproduce

  1. Have an active UEFN project connected to Revision Control (Lore)
  2. Experience a crash during a revision control operation (e.g. check-in/sync)
  3. Relaunch UEFN and attempt to reconnect to Revision Control on the same project
  4. Attempt to connect to Revision Control on a brand-new project as well

Expected Result

Revision Control should reconnect successfully, or at minimum recover/report a clear, actionable error. New projects unrelated to the crash should be unaffected.

Observed Result

Connection fails on the originally affected project AND on every new project created afterward, with:

Failed to deserialize revision states: Not found | NotFound(Traced { inner: NotFound, trace: Trace { locations: [Location { file: “lore-revision\src\state.rs”, line: 546, column: 37 }] } })

Lore.log shows the actual failure one step earlier:
[lore_storage::compress] Oodle decompress failed: 0
[lore_storage::read] Fragment fb62bd84e15c4d108528d07e9d69454664883290b4acd1a433e0785f337b9627 failed decompression/verification

Occurs when querying staged/pending status (staged:1, sync_point:1).

Repository ID: 9f5fa9ab463a93973bcd61b4891f26cd
Identity: 019bfb7e90617472ab2b3984e7def57f
Backend: urc-uefn.live.ucs.on.epicgames.com

Fully local reset performed with no effect (deleted project .lore folder, wiped UnrealEditorFortnite, reinstalled UEFN, cleared Launcher webcache, renamed global lore/urc cache folders — fresh empty local client hits the identical error instantly). This confirms the corrupted fragment is stored server-side, tied to my account, likely a leftover staged change from the original crash.

Platform(s)

PC / Windows

Upload an image

Zrzut ekranu 2026-07-18 190712.png
Zrzut ekranu 2026-07-18 190712.png1352×185 4.53 KB

2

Hi @HuBii_2093 could you please zip/attach your logs folder found at C:\Users\USERNAME\AppData\Local\UnrealEditorFortnite\Saved\Logs?

3

Logs.zip (8.6 MB)

4

Thank you for replying @HuBii_2093 I’ve logged this for the team to investigate

5

i have this same issue, i’ve tried remove my .lore folder as well but it just gets stuck loading at 100%, and my new project keeps disconnecting and reconnecting to revision control whenever i change anything

8

Same issue. Can’t check in my changes to the other team = map broken. pls fix asap

image
image1521×822 325 KB

9

Hi @Neo_1811 sorry to hear you’re also hitting this - could you please similarly zip/send your logs folder?

Are you still stuck or did you manage to find a workaround?

10

Unfortunatly I have still the issue. Somehow i can’t send my folder cause i am new.

11

Same thing for me

12

FORT-1129923 has been added to our ‘To Do’ list. Someone’s been assigned this task.

13

@Neo_1811 @Gr1Squid if you’re not able to attach the folders here please feel free to send them to me in discord at epic_garren

14

sended the files. when can i aspect the fix?

15

Thank you @Neo_1811 this will be helpful for our team to investigate the issue.

I cannot comment on a fix timeline unfortunately until we know what is happening, but we’ll keep you posted.

16

@C_elebi I missed your reply above - are you still experiencing this and is it occurring on one project or all of your projects?

17

Also @HuBii_2093 checking in whether you’re still experiencing this on all projects? We’ve yet to be able to reproduce that case but are still investigating

18

On other projects it started working again, but on that one project where that issue happend its still not working

19

Glad to hear its not all projects anymore @HuBii_2093

For the remaining problematic one could you try using the command line to run lore status --reset on the project folder?

There’s more information on how to set up and use the Command Line if you haven’t used them before"