UEFN Platform Cook fails with invalid_results on custom map

Summary

UEFN platform cook fails repeatedly with invalid_results after updating a large, detailed Japanese house map. Map Check warnings (non-streaming actors referencing streaming actors) were fully resolved (0 errors, 0 warnings), and a corrupted orphaned uasset in ExternalActors was manually removed, but the cook still fails with the same error.

Please select what you are reporting on:

Creative

What Type of Bug are you experiencing?

Assets

Steps to Reproduce

  1. Open the project and start a session
  2. Platform cook fails with: “Failed to cook server/client request” + invalid_results
  3. Confirmed Map Check shows 0 errors/0 warnings
  4. Confirmed a corrupted orphaned uasset file in ExternalActors was found and removed
  5. Cook still fails with the same invalid_results error after removal

Expected Result

Session loads successfully after platform cook completes

Observed Result

Platform cook fails repeatedly with invalid_results, session cannot start

Platform(s)

windows

Additional Notes

Windows Fortnite build version 42.10. Project is a large, detailed custom map with many custom devices/props. Happy to provide the CookJobId or additional logs if needed.

Additional findings after further investigation:

  1. Server-side 502 error from the cook API:
    LogOnline: Warning: MCP: Http Unexpected Result: HttpResult: 502 Code: 0
    Error: Failure ErrorCode=errors.com.epicgames.online.generic.http_error_400:valkyrie-cook-api.prod.ucs.on.epicgames.com
    “errorCode”: “http_error_400:valkyrie-cook-api.prod.ucs.on.epicgames.com”
    “errorMessage”: “[DEP] valkyrie-cook-api.prod.ucs.on.epicgames.com returned unexpected error http_error_400”

  2. Project file read error:
    LogValkyrie: Warning: プロジェクトファイルに誤りがあります (Project file has an error)
    [path]/residence.uefnproject
    Null Stream Line: 1 Ch: 0

  3. This issue is NOT limited to a duplicated/test project. I confirmed the same errors occur on the original main project as well, ruling out corruption from duplication.

Requesting further investigation, as the server itself (CachedInnerErrorType:Unknown) cannot determine the root cause.

The status of FORT-1153810 changed to ‘Needs Triage’. We are routing this to the appropriate team for investigation.

1 Like