Getting LogValkyrie error

Summary

I’m getting the following error when trying to launch my project in Unreal Engine:

LogValkyrie: Error: FlowStep_ResolveSessionCandidates():
Candidate module [647dfbf5-4bef-e1e9-4d6a-9f82b8b6a01f] failed validation with error:
[errors.com.epicgames.pre-processing.download_failure]

  • The issue originally started with an older map I was trying to upgrade.

  • Every time I make any type of change to that map and try to launch, I get the error above.

  • However, if I revert to the last saved Unreal revision (snapshot), the project launches with no issues.

  • I initially thought the map was the problem, so I created a new map from scratch, but I’m still getting the same error when I try to launch it.

What could be causing this error, and how can I fix it?

I’ve already verified UEFN, and Fortnite.
Reinstalled both from scratch
Flushed DNS
Changed Internet Settings back to default
Reset the modem
Tried on old maps, i can launch with no issue, if i make changes then it gives me the module error

Please select what you are reporting on:

Creative

What Type of Bug are you experiencing?

Other

Steps to Reproduce

Create a new map, do anything and try to launch, I just want to know if this is an Epic Servers issue or its my PC having this issue

Expected Result

The same error if its epics server fault

Observed Result

Only happens in old maps when i make any change

Platform(s)

Computer

FORT-972568 has been created and its status is ‘Unconfirmed’. This is now in a queue to be reproduced and confirmed.

Here’s what I’ve already tried:

  • Validated assets in UEFN (reports completed, no issues).

  • Verified UEFN and Fortnite installations.

  • Reinstalled both UEFN and Fortnite.

  • Factory reset my machine.

  • Logged in on another machine (same issue).

  • Used another account (works fine, which suggests the issue is account-specific).

  • Checked Verse (no errors reported).

  • Tried creating new maps/projects (still cannot launch).

    Mind you im also getting these errors right after the module error

    LogEOSSDK: Warning: LogHttp: 000001861CF9F000: HTTP request timed out after 30.00 seconds URL=https://api.kws.ol.epicgames.com/v1/playtime/account/d0dcfaef7cca48faa1ffb0fdf8d70560/product/3fd15bc288014f698cca1a3d1f01c7af/heartbeat
    LogEOSSDK: Warning: LogHttp: 000001861CF9F000: request failed, libcurl error: 0 (No error)
    LogEOSSDK: Warning: LogHttp: 000001861CF9F000: libcurl info message cache 0 ( Trying 3.165.181.98:443…)
    LogEOSSDK: Warning: LogHttp: 000001861CF9F000: libcurl info message cache 1 (Connected to api.kws.ol.epicgames.com (3.165.181.98) port 443)
    LogEOSSDK: Warning: LogHttp: 000001861CF9F000: libcurl info message cache 2 (ALPN: curl offers http/1.1)
    LogEOSSDK: Warning: LogHttp: 000001861CF9F000: libcurl info message cache 3 (ALPN: server accepted http/1.1)
    LogEOSSDK: Warning: LogHttp: 000001861CF9F000: libcurl info message cache 4 (using HTTP/1.1)
    LogEOSSDK: Warning: LogHttp: 000001861CF9F000: libcurl info message cache 5 (We are completely uploaded and fine)
    LogEOSSDK: Warning: LogHttp: 000001861CF9F000: libcurl info message cache 6 (schannel: remote party requests renegotiation)
    LogEOSSDK: Warning: LogHttp: 000001861CF9F000: libcurl info message cache 7 (schannel: renegotiating SSL/TLS connection)
    LogEOSSDK: Warning: LogHttp: 000001861CF9F000: libcurl info message cache 8 (schannel: SSL/TLS connection renegotiated)
    LogEOSSDK: Warning: LogHttp: 000001861CF9F000: libcurl info message cache 9 (Closing connection)
    LogEOSSDK: Warning: LogHttp: 000001861CF9F000: libcurl info message cache 10 (schannel: shutting down SSL/TLS connection with api.kws.ol.epicgames.com port 443)
    LogEOSSDK: Warning: LogHttp: Retry exhausted on https://api.kws.ol.epicgames.com/v1/playtime/account/d0dcfaef7cca48faa1ffb0fdf8d70560/product/3fd15bc288014f698cca1a3d1f01c7af/heartbeat
    LogEOSSDK: Warning: LogEOS: Failed to connect to the backend. ServiceName=[PlaytimeTracking], OperationName=[PlaytimeControllerHeartbeat], Url=

@H6D6S Could we have your project ID please? Feel free to send it to me in a DM.

Ignore the above, we have it. :slight_smile:

Hi! We’ve taken a look at this, and it appears there might have been an issue with the temporary storage space we use when uploading your project. We’ve cleared this out so if you try again you should find it works. If that turns out not to be the case, please let us know and we can investigate further!