Hey, Got an odd error when using uSync migrations. I get the ‘this document is published but is not in the cache’ on any node that I’m trying to publish even if it’s a new doc type that has nothing to do with migrated doc types / data types. Here’s the steps I’ve taken to hopefully make this clearer: - Install clean v13 latest - Create new doc type ‘HomeTest’ and allow at root - Add test Home node based on ‘HomeTest’ and check publishes ok (it does obviously) - upload uSync migrations zip file created from our V8 Project - Convert zip file so that all doctypes / data types are imported into the v13 project - Add a new node based on the ‘HomeTest’ (note this DocType is brand new in v13 and has 0 properties and has nothing to do with any data type / doc type we’ve imported from v8) - Result - “this document is published but is not in the cache’ So something in the DocTypes / DataTypes that have been imported from v8 is stopping nodes being published properly, even though the Doc Type is brand new and has no properties. How is this possible? 🙃 Can’t figure out what could be stopping the node publishing. We have over 100 DocTypes and a whole bunch of DataTypes that get imported from v8 so hard to figure out which one is causing the issue. Any help appreciated

Hi, I've never looked before but apparently the "this document is published but is not in the cache" is caused by the parent not being there or not being published it comes from here https://github.com/umbraco/Umbraco-CMS/blob/d4188022af2a0c7d8ebc6214ff4ed1d29f7865ed/src/Umbraco.Core/Routing/UrlProviderExtensions.cs#L198-L226 is is the "parentNotPublishedAnomaly" message. so it looks like it comes from the parent of an item not being published (potentially in the correct culture). ? not sure if that helps but its somewhere to look ? maybe republishing the parent item would help?

Thanks Kevin, something rouge with the languages, I deleted one of the languages and the everything was fine. Many thanks 🙂