I have a project, and whenever I try to check it in, it fails with the following log:
SourceControl: Error: Request put failed: Server returned error 3 for put of fragment Fragment { flags: 4, size_payload: 9360, size_content: 84971 } with payload size 9360 bytes
SourceControl: Error: Failed to store fragments, remote error: Request put failed: Server returned error 3 for put of fragment Fragment { flags: 4, size_payload: 9360, size_content: 84971 } with payload size 9360 bytes
SourceControl: Error: Failed to put fragment for 1426eadb7d4aa426543e8e06e54469303e7ca068baccfb7eb29db8415a1e8a7c-0198c648859272f09e637a890345c88b: Failed to store fragments, remote 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
The one way i can think of to reproduce this is by not checking in the project for a long time.
Expected Result
I think it’s very inconsistent. Once it happens, you can’t get rid of it, and sometimes it might not even occur twice in a row.
Observed Result
Whenever you try to check in, it won’t work, but both private island upload and publishing will still work.
It’s not about moving the URC folder to desktop. It’s just removing the urc folder and trying to check in. As far as understood the process. But that did not work for me apparently.
dont understand what you mean. to clarify: I have only 3 snapshots for this project. there are no hidden or filtered-out snapshots. numbers are wrong but I hope its not a big deal
With this release, we’re rolling out a new version of Unreal Revision Control (URC). Starting today, all new projects will use it by default. Existing projects will be migrated gradually over the coming weeks and months.
For now, this change is on the backend and your experience will mostly remain the same. This is an important technological change because the new system lays essential groundwork for future enhancements.
One immediate benefit of this change is Automatic personal backups: every save creates a remote backup to a personal branch, offering a safety net for disaster recovery. This means your work remains accessible even if it hasn’t been checked in. These backups can be viewed through the updated command line interface (CLI).
A side effect of personal backups, you may notice gaps in snapshot numbers in the Snapshot History panel. This is expected — personal backups also generate revision numbers, but only main project revisions appear in the panel at this time.
