Critical TEDS Assertion Failure: "Another row has already been registered" locking Verse Asset Registry

Summary

My published project (TheBackroomsGunGame) is currently hard-locked by a persistent Assertion Failure in the Typed Element Database (TEDS). The error Another row has already been registered under key occurs specifically when interacting with migrated folders (MasterAssets, RankMaterials, RankModels), while other project folders remain unaffected.

This registry collision prevents Verse from generating its asset digest, resulting in global Error 3506 (Unknown identifier). I have already cleared all local and global caches (%LOCALAPPDATA%, Intermediate, Saved) and performed a fresh project download from the URC Cloud Hub, but the corruption persists, suggesting a server-side or manifest-level registry lock tied to this specific Island.

Please select what you are reporting on:

Unreal Editor for Fortnite

What Type of Bug are you experiencing?

Stability

Steps to Reproduce

  1. Open the project TheBackroomsGunGame.

  2. Attempt to interact (rename, move, or build Verse) with the specific folders: MasterAssets, RankMaterials, or RankModels.

  3. The editor immediately triggers an “Assertion Failed” error: Another row has already been registered under key…

Note: Renaming any other project folder (not related to the migrated assets) works correctly and does not trigger the error.

Expected Result

The Asset Registry should allow modification and indexing of all project folders. Verse should recognize these folders as valid modules.

Observed Result

A specific registry collision occurs only with the migrated folders (MasterAssets, RankMaterials, RankModels). The logs show a TEDS collision:
Assertion Failed: Another row has already been registered under key ‘/TheBackroomsGunGame/[FolderName]/…’.
This specific lock prevents Verse from generating the digest for these modules, resulting in persistent 3506: Unknown identifier errors.

Platform(s)

PC / Windows

Island Code

9587-5263-2775

Additional Notes

I have isolated the issue to these specific folder names. I have already attempted:

Targeted Troubleshooting: If I rename unrelated folders, the editor works fine. The crash only happens with the folders required for the Rank System.

Manual Code Cleanup: Removed all manual module: definitions.

Cache Clearance: Deleted %LOCALAPPDATA%/UnrealEditorFortnite/ and project-level Intermediate/Saved folders.

Fix Up Redirectors: Ran the tool on the root and subfolders with no success.

Fresh Download: Deleted the local project and re-downloaded from URC Cloud. The specific registry lock on these three folder names reappears instantly.

It appears the TEDS (Typed Element Database) has “ghost” entries for these specific paths in the cloud manifest of this Island ID. I need a manual reset of the Asset Registry keys for MasterAssets, RankMaterials, and RankModels.

CRITICAL UPDATE: I have confirmed this is a global project failure, not asset-specific. Even adding a brand-new folder and a simple Verse script triggers the same ‘Unknown identifier’ error. The Asset Registry is completely unable to register new paths due to the Assertion Failed: Another row has already been registered error. The project is in a permanent deadlock where no new Verse modules can be recognized."

hi @AlexmaxFP ,

My experience is an INDIE DEV, so you try these potential answer at your own risk.

The island plays on Fortnite PC Windows 11.

My UEFN works on my Published Project

Therefore look at the changes in the Content , be careful deleting/changing as there is NO WAY back and you published version lives here in

UEFN - Content Service

First try Archiving Project

Then try restoring back from Archiving.

Examine the Verse check for any corruption moving to Verse menu

Export the Verse, then if you are sure the delete, then import the data.

Just be careful because this is where your published version lives.

If this does not fix this then vote this up and hopefully Epic Support will help

1 Like

I’ve tried all the steps you suggested: Archiving the project, restoring it, and even a full manual clean of the local cache and Verse folders. It still doesn’t work.

This map has NEVER had a single line of Verse code in any published version. I am implementing Verse for the first time in this island now. There is no ‘legacy’ Verse code or published Verse logic that could be causing a conflict.

The URC/Asset Registry is behaving as if the primary Verse path is occupied or corrupted, even though the island was originally built and published without Verse.

hi @AlexmaxFP ,

There is something complex beyond my skill, Vote up in Top right and hopefully someone might have seen this

1 Like