Since we upgradedto 10.0.8 we often receive the database timeout error when trying to manage the content in the backoffice. The error does not hapen when browsing the public site, only when browsing the backoffice. Anyone encountered something similar or have an idea what could be causing this? This happens only on production & test sites. It doesn't happen locally. Example: Microsoft.Data.SqlClient.SqlException (0x80131904): Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding. ---> System.ComponentModel.Win32Exception (258): The wait operation timed out. at Microsoft.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction) at Microsoft.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose) ... Timestamp 2024-02-24T21:19:36.220254+00:00 @MessageTemplate Exception ({InstanceId}). InstanceId f2a030e8 SourceContext Umbraco.Cms.Infrastructure.Persistence.UmbracoDatabase ActionId 6a73d7c1-9b69-48db-935c-f754d5233ab1 ActionName Umbraco.Cms.Web.BackOffice.Controllers.TrackedReferencesController.GetPagedDescendantsInReferences (Umbraco.Web.BackOffice) RequestId 4000072f-0005-c500-b63f-84710c7967bb RequestPath /umbraco/backoffice/umbracoapi/trackedreferences/GetPagedDescendantsInReferences ProcessId 21968 ProcessName w3wp ThreadId 76 Log4NetLevel ERROR HttpRequestNumber 417

Does it happen when you do anything specific, or is there no pattern to what triggers it?

No pattern. Just now it happened when we deployed changes to production. Sometimes we try to access the back office and it does not load or, most commonly, the folder tree on the left does not show up and the db error is thrown. This happened both in version 10 (10.8.3 or lower) and now in version 13.2.1 which we released yesterday.