Cook error due to timeout reached blocking sessions and private island codes from loading

General Issues and Bug Reporting
, , ,
1

Summary

For the past two days, in the morning we have been able to launch sessions but during the day we are getting cook errors due to timeout reached. Our project size was at 78% yesterday and we reduced it down to 69% last night and even at 69% we’re still getting this error. We’re not sure if it really has to do with project size but our download amount is like 290mb, which is well under the 400mb limit. Any idea what else we could do to try and resolve this?

Please select what you are reporting on:

Creative

What Type of Bug are you experiencing?

Assets

Steps to Reproduce

Try to load session. Wait for 30-45 minutes until it fails and presents a cook error.

Expected Result

I expect a session to properly load if Project Size is below 100%

Observed Result

Getting a timeout reached cook error when trying to launch a session. Creating a private island code also isn’t working. The code will load for 30 min - 1 hour and then fail.

Platform(s)

All

Upload an image

image (6).png
image (6).png1537×204 6.16 KB

3

We got our project down to 67% this morning and sessions were working early in the morning again. And yet again around peak hours (3PM ET) we are once again seeing cook errors. Seems like it might be tied to fortnite servers being overloaded?

4

@Flak Any insights on this? We’re still getting constant time out cook errors at 69% project size. This is blocking us from being able to perform a memory calculation test to release our game.

5

Could we get your project ID so we can do some further investigation?

6

@Flak our project ID is: c5514e69-4ca4-aaba-3b7b-7fb1908eb1fc // We managed to get rid of the cook error yesterday by lowering our project size back to 67%. But as soon as we’re at like 68% again we get the cook error.

7

Getting cook error again today even though nothing changed since yesterday when it was working.

8

@Flak We have project size down to 65% and are still getting cook error, which is blocking us from being able to release the game.

9

@Flak We have reduced down to 55% project size and we’re still getting cook errors constantly.

10

I passed your info over to the devs.

11

Thanks @Flak . Let me know if they need anything else to help. It took our main dev 6 hours on Friday to successfully launch a session. They got the cook error over and over and then luckily didn’t one time. That’s how it has been for the last two weeks. We’re needing to spend like an entire business day to just launch a session once, which is greatly hindering our development capabilities.

13

Thank you! Do you happen to know if there may be a particular asset or setting causing this? Is there anything we can do to workaround this issue while you investigate a fix? We were planning to release the game on Thursday but we’re having a lot of trouble right now launching a session.

14

We were hopeful the update yesterday might have fixed the issue but it did not. We’re still frequently getting cook errors. @Flak

15

@Flak Any updates on this? We’re still seeing this error constantly.

16

FORT-981124 has been added to our ‘To Do’ list. Someone’s been assigned this task.