uSync import failed: The existing DocumentCultureVariationDto was not found

JoppeRuessink · July 25, 2025, 11:20am

I’m getting the above error when importing my uSync settings. It looks like it fails on a node in language 2 that hasn’t been published in that language, but is published in another language. When I unpublish the node (which is a step further than “not created”), it seems to work.

What I don’t understand is why this error occurs during the settings import, because to me this seems like it’s related to content rather than settings.

So my more general question is: what exactly does this error mean?

Greetings,
Joppe

KevinJump · July 25, 2025, 12:18pm

Hi ,

Not 100% why it errors (will see if i can recreate).

but to answer why it happens on a settings import.

if you import changes properties in a document type, then there are internal umbraco events that fire and updates properties and content items and this is likely where the error is.

…

just looking at the code ,the error comes from a method called RenormalizeDocumentEditedFlags

github.com/umbraco/Umbraco-CMS

src/Umbraco.Infrastructure/Persistence/Repositories/Implement/ContentTypeRepositoryBase.cs

a2cc6a0a8


      
          /// <remarks>
          ///     If this is not done, then in some cases the "edited" value for a particular culture for a document will remain true
          ///     when it should be false
          ///     if the property was changed to invariant. In order to do this we need to recalculate this value based on the values
          ///     stored for each property, culture and current/published version.
          ///
          ///     Some of the sql statements in this function have a tendency to take a lot of parameters (nodeIds)
          ///     as the WhereIn Npoco method translates all the nodeIds being passed in as parameters when using the SqlClient provider.
          ///     this results in to many parameters (>2100) error => We need to batch the calls
          /// </remarks>
          private void RenormalizeDocumentEditedFlags(
              IReadOnlyCollection<int> propertyTypeIds,
              IReadOnlyCollection<int>? contentTypeIds = null)
          {
              var defaultLang = LanguageRepository.GetDefaultId();
          
              // This will build up a query to get the property values of both the current and the published version so that we can check
              // based on the current variance of each item to see if it's 'edited' value should be true/false.
              var whereInArgsCount = propertyTypeIds.Count + (contentTypeIds?.Count ?? 0);
              if (whereInArgsCount > Constants.Sql.MaxParameterCount)
              {

specifically here :

github.com/umbraco/Umbraco-CMS

src/Umbraco.Infrastructure/Persistence/Repositories/Implement/ContentTypeRepositoryBase.cs

a2cc6a0a8


      
              // This should never happen! If a property culture is flagged as edited then the culture must exist at the document level
              throw new PanicException(
                  $"The existing DocumentCultureVariationDto was not found for node {ev.Key.nodeId} and language {ev.Key.langId}");
          }

my quick reading of this is - the property contains a definition for a language that isn’t there.

so maybe - on your settings import you are removing languages and that is why the property error throws or your content has been synced with languages that are not installed on the site and the rebalencing is throwing this up.

editing the content will like be fixing this as only the valud languages will be getting saved back.

still not 100% sure - will need to play with it a bit

Update
Just to add -

this code is fired in umbraco when a property goes from being not vary by culture to vary by culture or the other way around. so that’s the change that is firing it,

JoppeRuessink · July 25, 2025, 12:33pm

Thanks Kevin for the swift response:
We recently changed some properties in this document type from ‘vary by culture’ to ‘shared’ and vice versa. That might be causing the issue. Is there anything we can do to resolve this?

Greetings,
Joppe

KevinJump · July 25, 2025, 2:39pm

Hi,

I am not sure - from the code i think its because one of the languages is missing , so maybe check all the languages that where previously installed are still there.

JoppeRuessink · July 28, 2025, 6:50am

Hi Kevin,

Thanks again for your swift response!

This does indeed seem to be the issue when I look at the value from the database table [dbo].[umbracoLanguage].
This is on the environment where I’m getting the error:

When I look at my local environment, where the error does not occur, I see this:

So it looks like the IDs for fr-BE don’t match.
Any idea how I can resolve this, without losing the already filled content on the environment where the error occurs?

Greetings,
Joppe

JoppeRuessink · July 28, 2025, 8:32am

Hi Kevin,

We’re considering doing a live-to-local sync, followed by a clean export on the local Umbraco environment. This should ensure that all files are properly aligned again and that we have the correct language IDs locally.

Before running the export, I’ll make the changes locally that currently can’t be applied on the pre-live environment, so we don’t lose any updates.

Sounds good, right?

Greetings,
Joppe

thomashdk · October 13, 2025, 1:16pm

Did you fix your issue?
Having the same.. @JoppeRuessink