@NoHoldsBarred Sorry for the inconvenience here. UEFN can sometimes take a long time to process in the cloud when there are a lot of assets, and a lot of specificially “expensive” types such as landscape, materials, textures and meshes. We’re going to take a look at the project in more detail and see if we can give you more specific recommendations as to how you could optimise it, and we’re also working on ways we could automatically feed this information to you directly in the editor; ideally while you’re authoring your project. We’re also always working on optimisations to the backend which will hopefully make this kind of issue a thing of the past.
Although it’s frustrating, it’s also worth pointing out that we cache a lot of the results we generate when processing the project, so if it does hit a limit and time out, we keep a lot of the results we generated so the next run should be quicker. I notice that after reporting this issue, your module has a seen a decent number of successfuly builds, although the overall time is still a lot higher than we’d like. This is also an indicator that the sheer quantity of assets is part of the problem, as well as perhaps a very complex level with lots of references! We’ll try and get back to you with some more specifics soon!