# umbracoDocumentUrl table not populating on save and publish

**URL:** <https://forum.umbraco.com/t/umbracodocumenturl-table-not-populating-on-save-and-publish/8653>\
**Category:** Questions\
**Tags:** v17\
**Created:** [October 13, 2026, 3:15pm UTC](https://forum.umbraco.com/t/umbracodocumenturl-table-not-populating-on-save-and-publish/8653 "2026-10-13T15:15:59Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![stephwillis1982nfu](https://forum.umbraco.com/user_avatar/forum.umbraco.com/stephwillis1982nfu/32/6372_2.png) [@stephwillis1982nfu](https://forum.umbraco.com/u/stephwillis1982nfu)\
**Post date:** [October 13, 2026, 3:16pm UTC](https://forum.umbraco.com/t/umbracodocumenturl-table-not-populating-on-save-and-publish/8653/1 "2026-10-13T15:16:00Z")

</div>

Issue,

Since applying a minor upgrade there or there abouts 17.6.2 have experienced issues publishing new articles on our website. This issue has persisted through to 17.7.1 which we are currently using.

We will publish an article, the link’s for that article will populate on the info tab.

The article will then appear on the website for a time.

However when something happens i.e. the app pool gets recycled over night for example, the links for that page, change to ‘This document is published but its URL cannot be routed’

I can fix it straight away by republishing the page, but the same issue will occur when the site bounces again.

When I publish the page, I monitor the [umbracoDocumentUrl] table in SMSS filtering by the guid for the node that I have just published, and nothing is populated for that guid in the table. (at all). Im pretty sure that it needs to do this in order for those urls to persist.

The table [umbracoContentVersion] does get updated when I save and publish by the way.

There are no error messages when click save and publish, nor are there any error messages in the logs folder.

I have reloaded the memory cache and rebuilt the database cache.

We did have an alert in the data integrity page a few weeks back which is been addressed.

That alert was:

Found 2 untrusted constraint(s). These indicate pre-existing data integrity issues that need to be resolved manually.

_Untrusted constraints prevent the SQL Server query optimizer from using them and indicate that orphaned or invalid rows may exist. Resolve the underlying data issue, then re-trust the constraint with ALTER TABLE … WITH CHECK CHECK CONSTRAINT._

_Foreign key FK\_umbracoDocumentUrl\_umbracoNode\_uniqueId on dbo.umbracoDocumentUrl_

_Foreign key FK\_umbracoDocumentUrl\_umbracoLanguage\_id on dbo.umbracoDocumentUrl_

After addressing this issue, the app has been restarted etc and the alert no longer appears, but thought I would mention it as I do think it may be related.

All the articles that have been published past the date of applying the aforementioned minor upgrade need their URL’s rebuilding pretty much on a daily basis at least, older articles are fine.

We’ve turned on some debug messages in serilog. Every time we save and publish it generates one of these.

{“@t”:“2026-10-13T14:25:01.8338774Z”,“@mt”:“Could not remove the document url cache. But the important thing is that it is not there.”,“@l”:“Debug”,“SourceContext”:“Umbraco.Cms.Core.Services.DocumentUrlService”,“ProcessId”:27928,“ProcessName”:“w3wp”,“ThreadId”:56,“ApplicationId”:“bfa88084c1661e8236aca829eea83eda2a339d0f”,“MachineName”:“xxxxx”,“Log4NetLevel”:“DEBUG”}

Cant see anything else in the logs that are worth sending to you.

The CMS url is correctly present in the appsettings cms routing part of the config files.

Any suggestions would be great because Im tearing my hair out at the mo.

Thanks

---

<div class="post-metadata">

**Author:** ![pc-pdx](https://forum.umbraco.com/user_avatar/forum.umbraco.com/pc-pdx/32/4457_2.png) [@pc-pdx](https://forum.umbraco.com/u/pc-pdx)\
**Post date:** [October 13, 2026, 3:21pm UTC](https://forum.umbraco.com/t/umbracodocumenturl-table-not-populating-on-save-and-publish/8653/2 "2026-10-13T15:21:59Z")

</div>

Hiya!  
This is an ongoing, very prevalent _thing_.  
I’ll link some other known threads that are related and may provide some insight, hope this helps!

> [@Umbraco 17 No Published Content](https://forum.umbraco.com/t/umbraco-17-no-published-content/8645/15):
>
> Hi @bythewiseman Ah, that would explain it! At least you figured it out in the end. Justin

> [@Umbraco 17 pages randomly becoming unpublished / returning 404](https://forum.umbraco.com/t/umbraco-17-pages-randomly-becoming-unpublished-returning-404/8486/12):
>
> Hi all, There’s an open issue here: Can you add to that issue as it will help HQ resolve it faster. Any info, diagnostics, details that may help would be useful. Justin

> [@Umbraco V17 - URLs are generated in the backoffice but not persisted to umbracoDocumentUrl](https://forum.umbraco.com/t/umbraco-v17-urls-are-generated-in-the-backoffice-but-not-persisted-to-umbracodocumenturl/8443):
>
> Hi, I’m experiencing an unusual URL/routing issue in Umbraco 17.6.1 and would appreciate some help understanding what is happening internally. Currently, I am working on a new project development in V17.6.1 so this is happening in my development environment, and deployment is handled through Azure DevOps. The behaviour is: I publish content from the Umbraco backoffice. The URL is generated correctly and works immediately. However, the generated URL is not written to the umbracoDocumentUrl t…

---

<div class="post-metadata">

**Author:** ![justin-nevitech](https://forum.umbraco.com/user_avatar/forum.umbraco.com/justin-nevitech/32/6219_2.png) [@justin-nevitech](https://forum.umbraco.com/u/justin-nevitech)\
**Post date:** [October 13, 2026, 3:29pm UTC](https://forum.umbraco.com/t/umbracodocumenturl-table-not-populating-on-save-and-publish/8653/3 "2026-10-13T15:29:11Z")

</div>

Hi @stephwillis1982nfu

As per this thread, can you make sure you’re not setting your instance to a subscriber role? It needs to be a publisher role to populate the umbracoDocumentUrl table.

> [@Umbraco 17 No Published Content](https://forum.umbraco.com/t/umbraco-17-no-published-content/8645/15):
>
> Hi @bythewiseman Ah, that would explain it! At least you figured it out in the end. Justin

Justin

---

<div class="post-metadata">

**Author:** ![stephwillis1982nfu](https://forum.umbraco.com/user_avatar/forum.umbraco.com/stephwillis1982nfu/32/6372_2.png) [@stephwillis1982nfu](https://forum.umbraco.com/u/stephwillis1982nfu)\
**Post date:** [October 14, 2026, 7:06am UTC](https://forum.umbraco.com/t/umbracodocumenturl-table-not-populating-on-save-and-publish/8653/4 "2026-10-14T07:06:38Z")

</div>

Thanks Justin and everyone above, that sounds interesting, let me grab a coffee and have a go! I’ll let you know what happens shortly!.

---

<div class="post-metadata">

**Author:** ![jacob](https://forum.umbraco.com/user_avatar/forum.umbraco.com/jacob/32/145_2.png) [@jacob](https://forum.umbraco.com/u/jacob)\
**Post date:** [October 14, 2026, 8:36am UTC](https://forum.umbraco.com/t/umbracodocumenturl-table-not-populating-on-save-and-publish/8653/5 "2026-10-14T08:36:48Z")

</div>

Hi all,

To close the loop on this from the HQ side: the pattern described here (published pages that work at first, then lose their URL and return 404 after a restart or deployment, with no rows in `umbracoDocumentUrl`) matches a bug that is fixed for 17.8.0 and 18.3.0. It’s tracked in [#23565](https://github.com/umbraco/Umbraco-CMS/issues/23565) and the fix is [#23943](https://github.com/umbraco/Umbraco-CMS/pull/23943). It has come up in a few threads, so I’m posting the same note in each.

**What’s going on**  
Since 17.4.2, a page’s URL is written to `umbracoDocumentUrl` only by the server that handled the publish, and that write was skipped whenever the server’s role was `Subscriber`. The catch is that the role decides which instance runs scheduled jobs, not which one serves the backoffice. So the instance your editors publish from can end up as a Subscriber, either through the automatic election or because it’s set in code. When that happens, every publish it handles is kept in memory but never saved to the database. The page works until the next restart and then returns 404. Republishing puts it back in memory, which is why it keeps coming back.

**Until 17.8.0 / 18.3.0 is out**  
Check that the instance your editors publish from is not a Subscriber. If it ended up as one through the automatic election, registering it explicitly as `SchedulingPublisher` avoids the problem until you can upgrade. If your own code registers it as a Subscriber, that setup isn’t supported and you’ll need to change it, upgrade or not. The [load-balancing docs](https://docs.umbraco.com/umbraco-cms/run-in-production/infrastructure-and-ops/server-setup/load-balancing/load-balancing-backoffice#server-role-accessor) say the backoffice server should be `SchedulingPublisher`.

**After upgrading**  
The fix stops new publishes from being affected, but it does not repair pages that are already missing their rows. To repair those once, either:

- publish with descendants from the root, on the instance that holds the publisher role, or
- delete the `UmbracoUrlGeneration` and `UmbracoUrlAliasGeneration` rows from `umbracoKeyValue` and restart one instance that isn’t a Subscriber. This forces a full URL rebuild on start-up, which loads every document, so expect a slower first start on larger sites.

If you still see this after upgrading and repairing, please open a new issue and reference #23565.

---

<div class="post-metadata">

**Author:** ![stephwillis1982nfu](https://forum.umbraco.com/user_avatar/forum.umbraco.com/stephwillis1982nfu/32/6372_2.png) [@stephwillis1982nfu](https://forum.umbraco.com/u/stephwillis1982nfu)\
**Post date:** [October 14, 2026, 8:55am UTC](https://forum.umbraco.com/t/umbracodocumenturl-table-not-populating-on-save-and-publish/8653/6 "2026-10-14T08:55:54Z")

</div>

Thanks Jacob, thats good news. We have one CMS on its own box, and two front end load balanced boxes for the front end. Previously we havent set up Subscribers and SchedulingPublishers explicitly, so I’m doing that right now to resolve the problem. Thank you for your support.

---

<div class="post-metadata">

**Author:** ![jacob](https://forum.umbraco.com/user_avatar/forum.umbraco.com/jacob/32/145_2.png) [@jacob](https://forum.umbraco.com/u/jacob)\
**Post date:** [October 14, 2026, 9:09am UTC](https://forum.umbraco.com/t/umbracodocumenturl-table-not-populating-on-save-and-publish/8653/7 "2026-10-14T09:09:53Z")

</div>

Sounds like a good setup for it: CMS server as `SchedulingPublisher`, the two front-ends as `Subscriber`. Once that’s in place, any pages that already lost their URL need publishing once more from the CMS server (publish with descendants from the root covers everything in one go).

---

<div class="post-metadata">

**Author:** ![stephwillis1982nfu](https://forum.umbraco.com/user_avatar/forum.umbraco.com/stephwillis1982nfu/32/6372_2.png) [@stephwillis1982nfu](https://forum.umbraco.com/u/stephwillis1982nfu)\
**Post date:** [October 14, 2026, 9:24am UTC](https://forum.umbraco.com/t/umbracodocumenturl-table-not-populating-on-save-and-publish/8653/8 "2026-10-14T09:24:49Z")

</div>

I’ve implemented load balancing properly now and its working well, Thank you all

---

<div class="post-metadata">

**Author:** ![cheeseytoastie](https://forum.umbraco.com/user_avatar/forum.umbraco.com/cheeseytoastie/32/1423_2.png) [@cheeseytoastie](https://forum.umbraco.com/u/cheeseytoastie)\
**Post date:** [October 20, 2026, 7:52am UTC](https://forum.umbraco.com/t/umbracodocumenturl-table-not-populating-on-save-and-publish/8653/9 "2026-10-20T07:52:24Z")

</div>

Interesting reading - and some good explanations.

Just for my own sanity can I triple check - if you’ve got v17 load balanced sites and you’ve ensured that only the SchedulingPublisher instance does any publishing your content should all be safe, you’re unaffected by this bug and there’s no need to do a truncate and full rebuild on that table for v17.8?

I’m asking as it sounds like some content could have subtly gone missing here - and no-one would notice for a few months, then suddenly it’s a bug no-one can explain!

I think the approach of not forcing the rebuild is a good call - just want to check the advice to do it is only if you’ve had mis-configured load balancing and seen some issues rather than - everyone who has a load balanced site should do this out of caution?

Thanks all - sounds like a tricky bug has been nailed here.

---

<div class="post-metadata">

**Author:** ![justin-nevitech](https://forum.umbraco.com/user_avatar/forum.umbraco.com/justin-nevitech/32/6219_2.png) [@justin-nevitech](https://forum.umbraco.com/u/justin-nevitech)\
**Post date:** [October 20, 2026, 8:10am UTC](https://forum.umbraco.com/t/umbracodocumenturl-table-not-populating-on-save-and-publish/8653/10 "2026-10-20T08:10:39Z")

</div>

Hi @cheeseytoastie

If you’ve set up load balancing with explicit server roles (your own IServerRoleAccessor pinning one instance as SchedulingPublisher) and the backoffice is only ever accessed on that instance, you should be fine. The issue in this thread was content being published from a Subscriber instance, which meant the umbracoDocumentUrl table wasn’t being populated. If you rely on the default role election, the publisher can change, so pinning it explicitly is the safer option.

Justin

---

<div class="post-metadata">

**Author:** ![cheeseytoastie](https://forum.umbraco.com/user_avatar/forum.umbraco.com/cheeseytoastie/32/1423_2.png) [@cheeseytoastie](https://forum.umbraco.com/u/cheeseytoastie)\
**Post date:** [October 20, 2026, 8:50am UTC](https://forum.umbraco.com/t/umbracodocumenturl-table-not-populating-on-save-and-publish/8653/11 "2026-10-20T08:50:03Z")

</div>

That’s exactly how I read it - was just triple checking. Basically because it won’t self heal - explaining missing content to a client a few months after it silently went missing is something I’d like to avoid (and seems like I can sleep easy!).
