Revision Control check-in fails with warning

Summary

UEFN displays the warning “Failed checking revision control status!” when attempting to check in with Unreal Revision Control, and I cannot commit changes.

Please select what you are reporting on:

Unreal Editor for Fortnite

What Type of Bug are you experiencing?

Unreal Revision Control

Steps to Reproduce

I can’t provide consistent steps, it’s only occurring on this project on my machine. It happens whenever I try to check in changes. I get the check in dialog and wait a few minutes for it to check in.

Expected Result

The check in should succeed.

Observed Result

A yellow warning appears: “Failed checking revision control status!”

Platform(s)

PC

Upload an image

Screenshot 2025-08-31 183712.png

@TheSmashersVEVO Sorry to hear you’re hitting this - could you please zip and send your logs found at C:\Users\USERNAME\AppData\Local\UnrealEditorFortnite\Saved\Logs either here or to me directly on discord at @epic_garren?

I’m seeing this issue happen now to me. Here are my logs:

@NoHoldsBarred thank you very much for sharing your logs. We will investigate this asap.

As a near-term workaround you can try the steps I posted here to get unblocked. https://forums.unrealengine.com/t/failed-to-load-fragment-payload-for/2621582/2?u=gxg_work

A note for this workaround: upon your first check-in after performing it, please carefully review the changes that appear in the submit dialog and right-click–>revert any changes you do not recognize.

While regenerating the URC folder helps work around issues like this, it means the context is lost on the last snapshot you had synced, so it is easy to push forward older states of files that your collaborators have since changed, overwriting their work unless you dig for it in the snapshot history.

Thank you! For now, the workaround fix I used was to delete the project off my computer and then re-sync it, but this does cause changes to be lost. To be safe, I’m just checking in very often so if it does happen I don’t lose too much work.

1 Like

This issue should be fixed in 37.30 when it is released. Please let us know if you continue to run into it thereafter. Thanks for your patience!

FORT-972390 is ‘Closed’ as ‘Fixed’. The issue will be addressed in 37.50.