As I mentioned on the livestream last week, I'd look into this and see where it was and chase it up if necessary.
The current status of this job is that we've found the cause and are working on resolving this. This one seems to be a tricky one as there is a mix between engine and content work involved. However it looks like we have found a solution that will only require a content change.