Error Persistence Verse Unable to update map already published

[scimmi4]

Hello,

I want to clearly explain what happened.

February 2025: My Fortnite Creative map was working perfectly. I had added an achievements system that uses persistent data in Verse. No publishing issues.

April 2025: Due to technical problems, I had to reset my PC. After the reset, when I reopened the project, the map was completely empty no Verse code, no 3D models, nothing. This happened because I had not activated Unreal Revision Control, so all local data was lost. From that moment on, every attempt to publish resulted in a Persistent Level Error.

May 2025: I tried every possible solution: restoring previous versions of the map, removing parts of the code, but the error always persists. I no longer have access to the old working Verse code for the same reason.

Current situation:

I can no longer publish updates for this map.

It was my only source of income, and without updates I am losing almost all my players.

I have already asked for help on the forums, Discord, Telegram, and other channels, but no solution was found.

I urgently ask for help:

Can you check and, if necessary, reset the persistent data of my map?

Is there a way to allow me to update it again without having to completely remake it from scratch?

I can immediately provide: the map name, island code, and screenshots of the error.

This issue is not just a bug it is putting my work and my only source of income at risk.

Thank you.

[im_a_lama (LAMA)]

you need to recreate the exact same persistence structure in verse, with the exact same variable names

[BRGJuanCruzMK]

Hey @scimmi4 how are you?

Exactly as @im_a_lama said, you need to recreate all the persistent data by yourself.

Here is a really good video with a lot of tips on how to avoid this kind of issues!

Hope this helps you!

[scimmi4]

This is not possible because having reset the PC and not having activated unreal revision control before doing so I do not have any previous saved versions and I do not have access to old codes and nothing I put back the old identical code that I had that used persistence but I still have the error is there no way to solve it??

[scimmi4]

Thanks for the video, but that’s not possible because I reset my PC and didn’t enable unreal revision control first. I have no previous versions saved and no access to old codes or anything. I reinstalled the old, identical code I had that used persistence, but I still get the error. Is there any way to fix it?
I also contacted the guy in the video, and he said I lost the map and there’s nothing I can do.

[im_a_lama (LAMA)]

That’s unfortunate, not using urc can be terrible, if you didn’t hard format your disk maybe you can try to recover the project.

You shouldn’t have recovered a corrupted version of your project in the first place which I’m not understanding (same project but only verse is missing? that’s weird), so I’m assuming you either had urc enabled and downloaded an old version or you had OneDrive or something activated or you had another project folder elsewhere

[scimmi4]

Hi, thanks for your reply. I want to clarify a few points about my situation:

• I never had URC enabled, so I cannot recover old versions from revision control.

• I did not format my disk. The problem happened directly inside UEFN after an error, and from that moment all Verse files disappeared/corrupted.

• I already checked OneDrive and other folders, but I don’t have any other copy of the project.

So this is not just a “wrong version” or “missing folder” problem. It’s a corruption issue inside the project, and that’s why I keep saying only Epic can fix this directly.

Is there any way to recover my map inside the same project without remaking everything from scratch? For example:

• resetting the persistence,

• wiping the corrupted data and keeping the project base,

• or any internal tool Epic has to restore the Verse part of a project.

I already sent multiple tickets to Epic, with screenshots of the errors, but they always redirect me to the forum without helping. I’m desperate to recover this project because it’s my first serious map, I’ve worked on it for months, and it’s very important to me.

Do you know if there’s any real solution, or any way to ask Epic to directly intervene on this project?

[im_a_lama (LAMA)]

If you can’t recover files on your disk, you could try to make a copy your map to a new project, this way persistence compatibility won’t occur

[scimmi4]

Thanks for your reply, but unfortunately creating a new project is not a real solution for me.

The reason is that this project already has player data, persistence, metrics and all the history of months of work. If I start from a new project, I basically lose everything and it’s like throwing away 9 months of progress.

That’s why I keep insisting that only Epic could help:

• by resetting persistence,

• wiping the corrupted Verse data,

• or restoring the Verse folder with internal tools.

Is there really no way to escalate this problem to the Epic UEFN team? Because regular support told me they “cannot do more,” but this means that right now I’m stuck with a completely broken project with no recovery options.

I just want to save this project instead of starting over.

[im_a_lama (LAMA)]

Try contacting the support, there is a form somewhere, maybe they’ll give you your persistence structure so you can make it again

[scimmi4]

Thanks for your suggestion, I really appreciate it. The problem is that I have already contacted Epic Support many times (at least 8 different tickets) and every single time they either close the ticket without answering or tell me they can’t do anything and redirect me to the forum.

So it’s not that I didn’t try: I tried everything possible with Epic directly, but they refuse to provide any solution or persistence data. That’s why I’m asking here, because I’m stuck in a loop where support sends me to the forum, and the forum tells me to contact support again.

Do you (or anyone here) know if there is a specific form or contact channel different from the normal support tickets, where Epic might actually share the persistence structure?

[im_a_lama (LAMA)]

I might have a solution for you, go to this website
UEFN - Content Service

Click on your project > Click on “Modules” > Click on the main module > Download the verse file that contains your persistence data (you can change the module version in the top right corner to a previous one if it doesn’t work)

[scimmi4]

Hi, thanks a lot for your help I think this could really be the key to fixing my persistence issue if I can restore the old Verse module, maybe the persistence will become compatible again.

The only problem is that when I try to download the Verse file from Content Service, I instantly get this error:

Cannot set properties of null (setting ‘href’)

I already tried with Chrome and Edge, normal and incognito, cleared cache etc., but it always happens the same.

Do you know if there’s a workaround for this bug, or another way to get the Verse module file from the Content Service?

Thanks again, your suggestion gave me some hope!

[im_a_lama (LAMA)]

F12 > Network > Click the file again > you should see something like this (picture) > double click the first link

[scimmi4]

Hi!

I wanted to give you an update and explain exactly what I’ve done:

I downloaded all the files from the April 29 version, which is the last version before I reset my PC and lost everything. This is therefore the last version with all the Verse codes working and compatible with persistence.

In my only Verse code out of 18 that used persistence, I had some errors because, at that time, I had renamed some folders differently compared to the original version. I want to clarify that I didn’t modify the Verse code itself—I just restored the original folder names that had been changed.

Now, after putting everything back exactly as it was before the PC reset, I no longer have any Verse errors. In theory, this should resolve the persistence issue and I shouldn’t receive the following error anymore:

"You cannot publish this version because your persistent Verse data is not backward compatible with your current published version."
verse_validate_publish_failed_weakmaps

Unfortunately, I won’t be able to check directly until October 4, because Epic has suspended my publishing privileges.

I also wanted to ask for clarification: do you think the different folder names could have been the cause of the persistence error? And regarding the other Verse codes that don’t use persistence, can I leave them as they are since they shouldn’t cause any problems, right?

Thanks a lot for all your help so far!

[im_a_lama (LAMA)]

Only the class you store inside your weak_map(player, XXX) should be restored (the class being XXX here), everything else can change