43.00: Release Verse Validation fails on old code from the live version (sys/published), new private version is clean

General Issues and Bug Reporting
, ,
1

Summary

Since 43.00 I cannot publish any update. Creating a release fails Verse Validation with an “Ambiguous identifier” error in a .verse file under sys/published/. The private version I submit does not contain that code: in it, the reported line is a comment and the identifier no longer exists anywhere. The editor’s Publishing Report passes for the same private version. The error seems to come from my live release’s code (published Nov 2, 2026 under 43.00), which itself passed validation at the time.

Error (my creator path, project name and module ID replaced with placeholders):

Module <module-id> in candidate link <private-version>?v=1 has error: "Ambiguous identifier; could be (/<creator>/<project>/server_events_device/LuckyStage:)Booths or (/<creator>/<project>/Models:)Booths" in file: "C:/build/FortniteGame/Plugins/GameFeatures/<module-id>/sys/published/Content/ServerEvents.verse" at line: 1210
verse_validate_publish_error

Exact codes and IDs are in the attached editor logs (Reference ID).

Please select what you are reporting on:

Creative

What Type of Bug are you experiencing?

Assets

Steps to Reproduce

  1. Live release was published on Nov 2, 2026 with UEFN 43.00. One .verse file had a local named “Booths”, and the project has a Content folder Models/Booths.
  2. Renamed that local so nothing is named after a Content folder. Verse builds clean in UEFN.
  3. Upload to Private Version. The editor’s Publishing Report says “Passed, Ready to Publish”.
  4. In Creator Portal, Publish > select that new private version.
  5. Verse Validation fails with the error above, pointing at sys/published/Content/ServerEvents.verse line 1210.
  6. Cleared the local upload cache (Intermediate/ValkyrieUploadTemp) and uploaded again: the server reuses the same module version and private link, and the release fails with the same error. An earlier private version failed identically.

Expected Result

Release validation compiles the private version I selected and passes, as the editor’s Publishing Report does.

Observed Result

Verse Validation fails on code that is not in the selected private version (the reported line in the submitted file is a comment). The file path is under sys/published/, so it looks like the live release’s code is being compiled and rejected. No update can be published; the live release stays up.

Platform(s)

windows