Blocker - Content-cooking Error UEFN

Presumably after the last UEFN Update (On 25th of August) my team is unable to Launch Session via Editor or enter the Island via Private Code because of a content-cooking error. I’ve already submitted a Bug Report form, but hope that someone might have information on this issue.

Every time we try launching session via Editor the following errors pop up:

  1. We encountered an error preparing your project. Error: errors.com.epicgames.content-service.cook-failure, An error occurred while communicating with the game servers (Content (re)cook error errors.com.epicgames.cookplugin.cookfailure.

  2. JOB_ID=43bf1bdd-9334-45c3-bef9-3de0475affac)., CookJobId:43bf1bdd-9334-45c3-bef9-3de0475affac

  3. Too many warnings / errors, aborted processing of errors / warnings

Here’s the Output Log:

And in Fortnite my character just keeps dying and respawning over and over, without the Island fully loading. Also there’s this message in the log about server failing to install new content:

Entering the Island via Private Code is now also impossible, each time we try the Matchmaking Error (#1) occurs and aborts matchmaking.
This only started occurring after the latest update. Our Island is within the size limits (around 200 MB) and I’ve already tried downscaling textures and removing irrelevant meshes from the map in hopes of reducing cookable content sizes, but that didn’t help. So we have no idea what could be causing this.
Also, reverting to previous snapshots became impossible (unless snapshots are of 25th of August). Trying to revert to earlier ones results in the following error: Snapshot retrieval failed. You have local conflicting changes.


Please help us out on this, I would greatly appreciate any advice/solutions.

Thank you for your report! We would like to look into this further, would you be able to submit a bug report using the form available here? Fortnite Creative
For more information, such as how to get the reference ID, please check out the article here: https://create.fortnite.com/news/using-the-creative-and-uefn-bug-reporting-form

I have submitted the report form already. Also, got an update:
I have finally managed to roll back to previous snapshots from last week via PowelShell and urc commands. The problem persists - it wouldn’t let us launch sessions on previous snapshots even though back when they were made everything was working.

Also having the same issue, here’s hoping Epic come back with something for us.

Same issue as in this thread Content (re)cook error , and we are also having it here. In the particular instance of that thread, it was a material that was at issue, and it’s the hypothesis we’re working with as we’re trying to get around it.

1 Like