There is a timeout setting on our server for when it is trying to process a SoundSet download… this is to avoid the server just getting completely stuck on a chain of SoundSets that have some technical glitch that completely stops them being processed… if enough of those built up then the rest of server performance would start to degrade.
Once you go past about 150MB with a SoundSet download size, you start getting near that time out mode on even a SoundSet with NO issues (when the server is GENERALLY busy = busy load times).
Sooo… I suppose, once you see your download getting close to 150MB, definitely consider splitting it in two (duplicate and delete). This will help you avoid things getting jammed int he future.
That said:
- it may have got jammed for a completely unrelated reason (actual Goblin with a spanner)
- We are always happy to help out by manually triggering a reprocess, like I did.
All makes sense?