Lockout on cooked content getting out of hand

I am getting this warning whenever I have to Push Changes and the number has been scaling depending on each project, but having to wait a minimum of 2 minutes each time I move a prop 1 point in the Z axis is a bit too much, I don’t know if I am doing something wrong to trigger that many of them, but when my map was on 10k memory it did 6 times 10s:

LogHttp: Warning: Lockout of 10.000000s on https://content-service.bfda.live.use1a.on.epicgames.com/api/content/v2/artifact/3d13db37-471e-4775-bc86-0ee0953a416a%3Apc/cooked-content

And when it is at 90k memory it dose like the image, 12 times, which is 12 x10 is 2 minutes.

And this map is the best example because in the worst case it was 8 minutes for every changes at minimum, because other times simply I got a timeout and had to wait another 8 minutes, and 15 min for every Push Change is completely impossible to work with.

The lines are very clear and I tried everything I found in the Froums, but nothing worked. It is cooking content to the cloud but its for this concrete artifacts “artifact/3d13db37-471e-4775-bc86-0ee0953a416a%3Apc” I think one time going through the different links this warnings say I found it was my scripts/creative custom devices. Maybe that is what is triggering too many of them (current hypothesis) or maybe it scales with verse code or maybe with pure memory usage.

I would like some intel on this artifacts and if anything can be done to lower this time, at this moment is the main problem on slowing my development.

@MiquelSangrador 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

I already did two months ago…

Did this ever get resolved? I am having the exact same issue. :frowning:

1 Like

Nothing new, old maps same minutes new maps at maximum 2 minutes, which is not bad but its every time you have to push so…

Affirmative. Same problem.

We also submitted this issue long time ago. We use this workaround:

UCB-1183 incident has been created. Status is ‘Awaiting Validation’.

@Stevie-Moon hey there, any news on this one? any tips to minimize this problem…? it is taking too much time of dev lifecycle…

thanks in advance