From 234b80b12fb55c906f72854016ea7cdb8e3574e7 Mon Sep 17 00:00:00 2001
From: Laura Neto <12862535+lauraneto@users.noreply.github.com>
Date: Wed, 10 Dec 2025 14:44:27 +0100
Subject: [PATCH] Use EagerWriteLock for long running operations

Switch from WriteLock to EagerWriteLock when acquiring the lock for
long running operations to ensure proper lock acquisition timing.
---
 src/Umbraco.Core/Services/LongRunningOperationService.cs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/Umbraco.Core/Services/LongRunningOperationService.cs b/src/Umbraco.Core/Services/LongRunningOperationService.cs
index 7c867c178ce2..c02272951df0 100644
--- a/src/Umbraco.Core/Services/LongRunningOperationService.cs
+++ b/src/Umbraco.Core/Services/LongRunningOperationService.cs
@@ -128,7 +128,7 @@ private async Task<Attempt<Guid, LongRunningOperationEnqueueStatus>> RunInner<T>
             {
                 // Acquire a write lock to ensure that no other operations of the same type can be enqueued while this one is being processed.
                 // This is only needed if we do not allow multiple runs of the same type.
-                scope.WriteLock(Constants.Locks.LongRunningOperations);
+                scope.EagerWriteLock(Constants.Locks.LongRunningOperations);
                 if (await IsAlreadyRunning(type))
                 {
                     scope.Complete();