# Lore: corrupted staged fragment breaks one repo (NotFound)

**URL:** <https://forums.unrealengine.com/t/lore-corrupted-staged-fragment-breaks-one-repo-notfound/2741953>\
**Category:** Issues and Bug Reporting\
**Tags:** open, unreal-editor-for-fortnite, crash, fortnite-creative, bug-report, fortnite\
**Created:** [August 7, 2026, 1:53pm UTC](https://forums.unrealengine.com/t/lore-corrupted-staged-fragment-breaks-one-repo-notfound/2741953 "2026-08-07T13:53:07Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![midnight7zz](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@midnight7zz](https://forums.unrealengine.com/u/midnight7zz)\
**Post date:** [August 7, 2026, 1:53pm UTC](https://forums.unrealengine.com/t/lore-corrupted-staged-fragment-breaks-one-repo-notfound/2741953/1 "2026-08-07T13:53:07Z")

</div>

### Summary

Revision Control (Lore) fails on one UEFN project with a misleading “NotFound” error. Lore.log shows the real cause one step earlier: a fragment fails Zstd decompression/verification — i.e. a corrupted staged-change fragment stored server-side, left over from a crash during a revision-control operation. A second repository on the same account is unaffected and syncs normally, which confirms the corruption is isolated to one repository’s staged state, not the local client. This appears to be the same issue tracked as FORT-1129923.

### Please select what you are reporting on:

Unreal Editor for Fortnite

### What Type of Bug are you experiencing?

Lore

### Steps to Reproduce

1. Have a UEFN project connected to Revision Control (Lore).
2. A crash occurs during a revision-control operation (e.g. check-in), leaving a corrupted staged change.
3. Relaunch UEFN and query status / attempt to reconnect on that project.

### Expected Result

Revision Control reconnects and reports status successfully, or recovers gracefully with a clear, actionable error (e.g. an option to discard the corrupt staged change).

### Observed Result

Any status query that reads staged state on the affected repository fails. UEFN surfaces:

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 real cause one step earlier:

[lore\_storage::compress] Zstd decompress failed: 18446744073709551606  
[lore\_storage::read] Fragment 8f291f20faed0af2656d76f54e29b3c65fda80303dea3bf7c5392ab31a34245c failed decompression/verification: failed to decompress fragment

It occurs specifically when querying staged status (staged:1, sync\_point:1) on the affected repository. A separate repository under the same identity completes status successfully (branch synchronized, revision 81), confirming the failure is server-side and isolated to the corrupted staged fragment. The affected repository’s last committed revision is intact — only the uncommitted staged state is corrupt.

### Platform(s)

PC / Windows

### Additional Notes

Details for the team

Identity: 01975155bdd171c995aedfaecd20aa30  
Affected repository: 450029d04993f1f1e0cfdb81cdf0c8a7  
Healthy repository (reference): 809c96e55e5b37d6810fcda2fbce8de6  
Corrupted fragment: 8f291f20faed0af2656d76f54e29b3c65fda80303dea3bf7c5392ab31a34245c  
Lore version: 0.8.1-nightly+3397  
Backend: [urc-uefn.live.ucs.on.epicgames.com](http://urc-uefn.live.ucs.on.epicgames.com)  
Related report: FORT-1129923

Note on local resets  
Since the fragment is stored server-side, local mitigations (clearing caches, reinstalling UEFN, deleting the local .lore folder) are not expected to resolve this — consistent with the existing report FORT-1129923, where a full local reset had no effect.

Request  
As the corrupted fragment is an uncommitted staged change and the last committed revision is intact, please discard/purge the corrupt staged change on repository 450029d04993f1f1e0cfdb81cdf0c8a7 (fragment 8f291f20…a34245c) so the client can resync from the last good revision. Full Lore.log attached.  
Uploading: Lore.log…

---

<div class="post-metadata">

**Author:** ![wouter](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/wouter/32/1036116_2.png) [@wouter](https://forums.unrealengine.com/u/wouter)\
**Post date:** [August 11, 2026, 7:35am UTC](https://forums.unrealengine.com/t/lore-corrupted-staged-fragment-breaks-one-repo-notfound/2741953/4 "2026-08-11T07:35:56Z")

</div>

> [@midnight7zz](#):
>
> staged

Hello @midnight7zz - sorry you’re in this state. We are investigating.

Could you run `lore.exe repository verify`in your project folder?

There’s [more information on how to do that here](https://dev.epicgames.com/documentation/fortnite/lore-version-control-command-line-interface-in-unreal-editor-for-fortnite) if you’re unfamiliar with command line tools.

---

<div class="post-metadata">

**Author:** ![Bug-Reporter](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/bug-reporter/32/1223650_2.png) [@Bug-Reporter](https://forums.unrealengine.com/u/Bug-Reporter)\
**Post date:** [September 24, 2026, 9:00am UTC](https://forums.unrealengine.com/t/lore-corrupted-staged-fragment-breaks-one-repo-notfound/2741953/5 "2026-09-24T09:00:49Z")

</div>

FORT-1137460’s status has changed to ‘Ready for QA’. A member of the QA department is investigating the issue.
