Evening Umbracians, I'm having trouble with a big content import causing write locks (that is, when editors try to save content during the import we get write lock errors) in Umbraco 10.8.3. The import either runs in the background or in a HTTP request (if triggered manually). We're mostly testing manually (via HTTP), so this isn't a background task issue. I've been reading around and I feel like I've eliminated the usual culprits: - It's not a load balanced environment, the instance does share a database with it's own staging instance but only briefly during deployment before swapping (could this be causing the problem?). - We call

EnsureUmbracoContext

in a using statement that wraps the whole operation. - Where we call

CreateScope

it's in a using statement and we call

scope.Complete()

. - I've double checked the relevant settings: -

Umbraco.CMS.Global.MainDomLock

=

FileSystemMainDomLock

-

Umbraco.CMS.Hosting.LocalTempStorageLocation

=

EnvironmentTemp

-

Umbraco.CMS.Examine.LuceneDirectoryFactory

=

SyncedTempFileSystemDirectoryFactory

A bit of context about the operation: - The service is transient. - We inject

IContentService

and

IPublishedSnapshotAccessor

(not using

IServiceProvider

). Is there any documentation/resources people would recommend? Happy for any questions/guidance 😅.