We are currently seeing the error "document is published but its URL cannot be routed" for a couple of collection nodes on our site which reappears every time the site is restarted, meaning these nodes and the functionality they provide break with each deployment/restart. This is occurring on Umbraco 13.3.2 on a site with a single language that is hosted in Umbraco Cloud, but the issue also occurs locally. The error is cleared by republishing the nodes with the routing issues along with their (already published) children, but restarting the solution brings the error back. The issue seems to be at least partially content dependent as it occurs on our staging environment but not our test site, and copying the dbs from each of these environments and running them locally results in the same behaviour. Has anybody seen a similar issue before? This is a more abstract description of what I've put in the other chat regarding Articulate, since I'm less convinced that this issue necessarily relates to that package specifically at this point.

No uSync content import going on at startup? No "conflicting" culture&hostname configurations?

Hey there - we don't have uSync in the solution, and the site is monolingual (en-gb) with only a single domain name and no specific domain configured. I tried adding a specific domain locally (configure home node as "localhost") but this didn't have any effect