UEFN cook error: Output Sentry Error Docker (This has been fixed now)

General Issues and Bug Reporting
, , ,
1

Summary

This has been happening to all of my bigger maps. I randomly get this cook error, and it feels similar to the memory cook issue where we have no idea what’s causing it or how to fix it.

The only workaround seems to be removing almost all assets and redoing a ton of hard work, just for the issue to eventually come back again.

If you need any logs, please let me know

Please select what you are reporting on:

Unreal Editor for Fortnite

What Type of Bug are you experiencing?

Project Size

Steps to Reproduce

A large environment with around 20,000–40,000+ actors

Expected Result

The cooker should successfully process projects that fall within Epic’s performance and memory limits, even when they include high actor counts

Observed Result

Projects exceeding roughly 30,000–40,000 actors frequently fail to cook resulting in “Output Sentry Error Docker” error

Platform(s)

PC, iOS, Android, PlayStation, Xbox, Nintendo Switch, Cloud platforms

Upload an image

HHKxiiaWoAAKV4f.png
HHKxiiaWoAAKV4f.png734×150 5.67 KB

Additional Notes

This issue, along with the memory cook problem, has been ongoing for so long that it’s now approaching a full year without any clear resolution. Despite multiple updates, it still hasn’t been properly addressed, and it continues to impact large projects in a major way.

For additional context, this started around the Star Wars season, and ever since then creators working on bigger maps have been running into the same problems with no reliable fix.

3

hi @Pokeasy

Epic support will need the UEFN full logs by dragging a copy to this thread

C:\Users\%USERNAME%\AppData\Local\UnrealEditorFortnite\Saved\Logs\UnrealEditorFortnite.log

just when the error occurred.

The other things to check is

Check and Allow Docker to use port 443** in Windows Firewall**

and then add 64GB Virtual Memory (pagefile,sys)

How to add 64GB Virtual Memory

4

Here are the logs if it helps

UnrealEditorFortnite.zip (211.0 KB)

1 Like
5

hi @Pokeasy

Thanks for that.

Something remote when trying to get Project size. from log at about line 9250 is the snippet

LogValkyrie: Display: ProjectSizeRequest::CancelFlow for 29264e33-499c-7953-d1c3-bfa03c7bcf8f - Content (re)cook error errors.com.epicgames.outputsentry.failure.
JOB_ID=9127bfc2-534c-49cb-853b-ab8b8d818f9d
PlatformCook: Error: We hit an error while cooking this content
PlatformCook: Error: cook_failure
LogValkyrieRequestManagerEditor: Detected cook failure, cook job id 9127bfc2-534c-49cb-853b-ab8b8d818f9d

There has been a request for Project Size and this has got an error at the remote server

errors.com.epicgames.outputsentry.failure.
```
Looking at another persons log got a more detailed error while  cooking

Output Sentry error: Docker container exited with non-zero exit code: 3221225477 (code: 3221225477).

Output Sentry error: Docker container exited with non-zero exit code: 3221225477 (code: 3221225477).

Hopefully Epic Support will be able to find out more detail.

6

This has been fixed now!

1 Like
7

The status of FORT-1096247 changed to ‘Needs Triage’. We’ve confirmed the issue and it’s waiting to be assigned to someone to fix it.