cannot launch session just stays on initiating for ages then get error

Summary

My project will not launch a session. Ive never seen this before and its driving me insane. Any other project works but this one does not. I reinstalled uefn done restarts ect and nothing. I haven’t even published it yet and now i have issues.

Please select what you are reporting on:

Unreal Editor for Fortnite

What Type of Bug are you experiencing?

Matchmaking

Steps to Reproduce

unsure

Expected Result

when i click launch session it works as other projects

Observed Result

it doesnt work

Platform(s)

windows

Additional Notes

LogHotfixManager: Error: [Item: 37] Wasn’t able to parse the data with semicolon separated values. Expecting 3 or 5 arguments but parsed 10.
LogHotfixManager: Error: [Item: 38] Wasn’t able to parse the data with semicolon separated values. Expecting 3 or 5 arguments but parsed 10.
LogHotfixManager: Error: [Item: 39] Wasn’t able to parse the data with semicolon separated values. Expecting 3 or 5 arguments but parsed 10.
LogHotfixManager: Error: [Item: 40] Wasn’t able to parse the data with semicolon separated values. Expecting 3 or 5 arguments but parsed 10.
LogHotfixManager: Error: [Item: 41] Wasn’t able to parse the data with semicolon separated values. Expecting 3 or 5 arguments but parsed 10.
LogHotfixManager: Error: [Item: 42] Wasn’t able to parse the data with semicolon separated values. Expecting 3 or 5 arguments but parsed 10.
LogHotfixManager: Error: [Item: 43] Wasn’t able to parse the data with semicolon separated values. Expecting 3 or 5 arguments but parsed 15.
LogHotfixManager: Error: [Item: 44] Wasn’t able to parse the data with semicolon separated values. Expecting 3 or 5 arguments but parsed 10.
LogHotfixManager: Error: [Item: 45] Wasn’t able to parse the data with semicolon separated values. Expecting 3 or 5 arguments but parsed 15.
LogHotfixManager: Error: [Item: 46] Wasn’t able to parse the data with semicolon separated values. Expecting 3 or 5 arguments but parsed 10.
LogHotfixManager: Error: [Item: 47] Wasn’t able to parse the data with semicolon separated values. Expecting 3 or 5 arguments but parsed 15.
LogHotfixManager: Error: [Item: 48] Wasn’t able to parse the data with semicolon separated values. Expecting 3 or 5 arguments but parsed 10.
LogHotfixManager: Error: [Item: 49] Wasn’t able to parse the data with semicolon separated values. Expecting 3 or 5 arguments but parsed 15.
LogHotfixManager: Error: [Item: 50] Wasn’t able to parse the data with semicolon separated values. Expecting 3 or 5 arguments but parsed 10.
LogHotfixManager: Error: [Item: 51] Wasn’t able to parse the data with semicolon separated values. Expecting 3 or 5 arguments but parsed 15.
LogHotfixManager: Error: [Item: 52] Wasn’t able to parse the data with semicolon separated values. Expecting 3 or 5 arguments but parsed 10.
LogHotfixManager: Error: [Item: 53] Wasn’t able to parse the data with semicolon separated values. Expecting 3 or 5 arguments but parsed 15.
LogHotfixManager: Error: [Item: 54] Wasn’t able to parse the data with semicolon separated values. Expecting 3 or 5 arguments but parsed 10.
LogHotfixManager: Error: [Item: 55] Wasn’t able to parse the data with semicolon separated values. Expecting 3 or 5 arguments but parsed 10.
LogHotfixManager: Error: [Item: 56] Wasn’t able to parse the data with semicolon separated values. Expecting 3 or 5 arguments but parsed 10.
LogHotfixManager: Error: [Item: 57] Wasn’t able to parse the data with semicolon separated values. Expecting 3 or 5 arguments but parsed 10.
LogHotfixManager: Error: [Item: 58] Wasn’t able to parse the data with semicolon separated values. Expecting 3 or 5 arguments but parsed 10.
LogHotfixManager: Error: [Item: 59] Wasn’t able to parse the data with semicolon separated values. Expecting 3 or 5 arguments but parsed 10.
LogHotfixManager: Error: [Item: 60] Wasn’t able to parse the data with semicolon separated values. Expecting 3 or 5 arguments but parsed 10.
LogHotfixManager: Error: [Item: 61] Wasn’t able to parse the data with semicolon separated values. Expecting 3 or 5 arguments but parsed 10.
LogHotfixManager: Error: [Item: 62] Wasn’t able to parse the data with semicolon separated values. Expecting 3 or 5 arguments but parsed 15.
LogHotfixManager: Error: [Item: 63] Wasn’t able to parse the data with semicolon separated values. Expecting 3 or 5 arguments but parsed 10.
LogHotfixManager: Error: [Item: 64] Wasn’t able to parse the data with semicolon separated values. Expecting 3 or 5 arguments but parsed 15.
LogHotfixManager: Error: [Item: 65] Wasn’t able to parse the data with semicolon separated values. Expecting 3 or 5 arguments but parsed 10.
LogHotfixManager: Error: [Item: 66] Wasn’t able to parse the data with semicolon separated values. Expecting 3 or 5 arguments but parsed 15.
LogHotfixManager: Error: [Item: 67] Wasn’t able to parse the data with semicolon separated values. Expecting 3 or 5 arguments but parsed 10.
LogHotfixManager: Error: [Item: 68] Wasn’t able to parse the data with semicolon separated values. Expecting 3 or 5 arguments but parsed 15.
LogHotfixManager: Error: [Item: 69] Wasn’t able to parse the data with semicolon separated values. Expecting 3 or 5 arguments but parsed 10.
LogHotfixManager: Error: [Item: 70] Wasn’t able to parse the data with semicolon separated values. Expecting 3 or 5 arguments but parsed 15.
LogHotfixManager: Error: [Item: 71] Wasn’t able to parse the data with semicolon separated values. Expecting 3 or 5 arguments but parsed 10.
LogHotfixManager: Error: [Item: 72] Wasn’t able to parse the data with semicolon separated values. Expecting 3 or 5 arguments but parsed 15.
LogHotfixManager: Error: [Item: 73] Wasn’t able to parse the data with semicolon separated values. Expecting 3 or 5 arguments but parsed 10.
LogHotfixManager: Warning: Only 52 of 95 assets were successfully patched from ‘AssetHotfix’ section in the Game .ini file. The patched assets will be forced to remain loaded. Any assets that failed to patch may be left in an invalid state! Failure may occur due to the plugin not being installed and mounted.
LogMaterial: Warning: Material /OG_Custom_Verse_Devices/Materials/Master_Material.Master_Material missing bUsedWithNanite=True! Default Material will be used in game.
LogMaterial: Warning: Material /OG_Custom_Verse_Devices/Meshes/Imports/GameReadyTruck/Material.Material missing bUsedWithNanite=True! Default Material will be used in game.
LogMaterial: Warning: Material /OG_Custom_Verse_Devices/Meshes/Imports/jeep_chereoke/NewMaterial.NewMaterial missing bUsedWithNanite=True! Default Material will be used in game.
LogMaterial: Warning: Material /OG_Custom_Verse_Devices/Materials/m_translucent.m_translucent missing bUsedWithNanite=True! Default Material will be used in game.
LogMaterial: Warning: Material /OG_Custom_Verse_Devices/Materials/Chrome/Master_Material.Master_Material missing bUsedWithNanite=True! Default Material will be used in game.
LogMaterial: Warning: Material /OG_Custom_Verse_Devices/Materials/MyLogo/Master_Material/Master_Material.Master_Material missing bUsedWithNanite=True! Default Material will be used in game.
LogMaterial: Warning: Material /OG_Custom_Verse_Devices/Meshes/Imports/m725Ambulance/NewMaterial.NewMaterial missing bUsedWithNanite=True! Default Material will be used in game.
LogValkyrie: Display: UValkyrieProjectSize::RequestProjectLimits received: PublishingMemorySize=225000000 PublishingDownloadSize=419430400 ProjectUploadSize=2147483648 FileCount=5120 IndividualFileSizeKb=5242880
LogValkyrie: ProjectSizeRequest::GetProjectUploadSize for 48fb0a7b-4762-dc41-c0a5-d0b88b219d8f
LogValkyrie: ProjectSizeRequest::GetProjectDownloadSize for 48fb0a7b-4762-dc41-c0a5-d0b88b219d8f
LogValkyrie: ProjectSizeRequest::GetProjectCookedSize for 48fb0a7b-4762-dc41-c0a5-d0b88b219d8f
LogValkyrie: ProjectSizeRequest::GetDependencyDownloadSizes for 48fb0a7b-4762-dc41-c0a5-d0b88b219d8f
LogValkyrie: ProjectSizeRequest::Completed for 48fb0a7b-4762-dc41-c0a5-d0b88b219d8f
LogCoopNotesSidePanel: Error: Invalid browser Widget when load completed
LogValkyrie: Gathering intermediate assets to delete took 0.0 seconds
LogValkyrie: Intermediate assets cleanup took 0.0 seconds in total
LogValkyrieSummary: Starting Project Upload - Content Service
LogValkyrieSummary: Syncing project OG_Custom_Verse_Devices
LogValkyrie: Saving project source control settings to disk took 0.00 sec
LogValkyrie: Syncing project OG_Custom_Verse_Devices with content service took 0.67 sec
LogHttp: Warning: Retry 1 on https://content-service.bfda.live.use1a.on.epicgames.com/api/content/v2/project/d161a879-47ca-d095-008b-94afbd1ce741/meta
LogHttp: Warning: Retry 2 on https://content-service.bfda.live.use1a.on.epicgames.com/api/content/v2/project/d161a879-47ca-d095-008b-94afbd1ce741/meta
LogHttp: Warning: Retry 3 on https://content-service.bfda.live.use1a.on.epicgames.com/api/content/v2/project/d161a879-47ca-d095-008b-94afbd1ce741/meta
LogHttp: Warning: Retry 4 on https://content-service.bfda.live.use1a.on.epicgames.com/api/content/v2/project/d161a879-47ca-d095-008b-94afbd1ce741/meta
LogHttp: Warning: Retry 5 on https://content-service.bfda.live.use1a.on.epicgames.com/api/content/v2/project/d161a879-47ca-d095-008b-94afbd1ce741/meta
LogHttp: Warning: HttpRetry: Resetting log verbosity to Warning due to requests being retried
LogOnline: Warning: OSS: Http Unexpected Result: HttpResult: 0 Code: 0 Error: Failure ErrorCode=errors.com.epicgames.online.generic.connection_failure, Message=Connection to the server failed., Raw=connection_failure
LogValkyrie: Error: Failed to update project metadata on content service
Failure ErrorCode=errors.com.epicgames.online.generic.connection_failure, Message=Connection to the server failed., Raw=connection_failure
LogValkyrieSummary: Project OG_Custom_Verse_Devices failed to update
LogValkyrieActivityTracker: Warning: Upload → Fail Activity: OG_Custom_Verse_Devices - Failed to update project metadata on content service. Error: Connection to the server failed.
LogValkyrie: Unable to play: Validation failed
LogValkyrieActivityTracker: Warning: Upload → Fail Activity: UploadProjects - All uploads failed with errors

Landed here looking up info on whether the hotfixmanager errors have any known impact. In your case, it looks like UEFN was unable to receive a response from the API call made to https://content-service.bfda.live.use1a.on.epicgames.com/api/content/v2/project/d161a879-47ca-d095-008b-94afbd1ce741/meta

Chances are, the API was temporarily down, but there’s a fringe possibility there’s an error condition on their end that results in a failure to return an error code if it doesn’t recognize the project ID. If you’re familiar with troubleshooting failed http calls, you might double-check that your PC is able to get a response from that address, e.g. go there with your web browser and check that you get the expected “No authorization header” response. If you get the response but UEFN continues to claim there’s no response, I’d normally suspect a firewall blocking UEFN access except that you claim other maps are working fine. Maybe double-check and let us know what happens.

i never had any issue it just stopped working. I made a copy of the map and it works fine again quick solution.