fix: don't investigate timeout errors as EF migration issues

IntelliTect · Dec 12, 2024 · cbeb5a5 · cbeb5a5
1 parent 5bc22f2
commit cbeb5a5
Showing 1 changed file with 5 additions and 3 deletions.
diff --git a/src/IntelliTect.Coalesce/Api/Controllers/ApiActionFilter.cs b/src/IntelliTect.Coalesce/Api/Controllers/ApiActionFilter.cs
@@ -13,6 +13,7 @@
 using Microsoft.Net.Http.Headers;
 using System;
 using System.Collections.Generic;
+using System.ComponentModel;
 using System.Data.Common;
 using System.Linq;
 using System.Net;
@@ -93,10 +94,11 @@ public virtual void OnActionExecuted(ActionExecutedContext context)
                             currentEx = currentEx.InnerException;
                         }
                         string message = messages.ToString();
-
+                        
                         if (
                             options.Value.DetailedEfMigrationExceptionMessages &&
-                            (context.Exception as DbException ?? context.Exception?.InnerException) is DbException
+                            (context.Exception as DbException ?? context.Exception?.InnerException) is DbException dbEx &&
+                            dbEx.InnerException is not Win32Exception { NativeErrorCode: 258 } // The wait operation timed out
                         )
                         {
                             var dbMessage = GetDbContextMigrationExceptionMessage(context);
@@ -199,7 +201,7 @@ private static string GetDbContextMigrationExceptionMessage(ActionExecutedContex
 
             if (messages.Count == 0) return "";
 
-            return string.Join(" ", messages) + " This is the likely cause of the following error:";
+            return string.Join(" ", messages) + " This is possibly the cause of the following error:";
         }
 
         public void OnResultExecuting(ResultExecutingContext context)