"document is published but its URL cannot be routed" on Articulate article/author nodes after site restart in specific environment

[eqtr-ab]

We are currently seeing the error "document is published but its URL cannot be routed" on the info tab of the Articles and Author collection nodes, the error is cleared by a cache rebuild (or republish) but reoccurs as soon as the site is restarted.

The issue only occurs on the staging environment within umbraco cloud, dev appears to be unaffected - when we restore a copy of each db locally the behaviour is the same, i.e. when running the site locally with the staging db the blog breaks with each restart but not with the dev db. This means that different dbs are behaving differently when run against the same codebase.

We have tried a few different potential solutions - updating to the latest version of Articulate had no effect, neither did setting a domain and culture for the site's root node. Do you have any advice on investigating/resolving this issue so we don't have to rebuild the cache or republish the nodes with each deployment?

This is happening with Umbraco 13.3.2.

[Shazwazza]

Is it because the local nucache file (i.e. published cache) is out of sync with what is in the DB?

[eqtr-ab]

Hi @Shazwazza I'm not sure. We had to resolve the issue by deleting the problematic blog root node, creating a new one, and migrating all of the existing content over.