fix: log corrupt KeyframeData row read failures as errors, not warnings

Per review feedback from cvium: failing to read/backup an entity due to corrupt underlying data is a significant event that should be surfaced as an error, not silently downgraded to a warning.
2026-07-18 16:47:23 +02:00
parent d7727224c2
commit 663a873e07
1 changed files with 1 additions and 1 deletions
@@ -374,7 +374,7 @@ public class BackupService : IBackupService
                                            }
                                            catch (Exception ex)
                                            {
-                                                _logger.LogWarning(ex, "Could not read next entity of type {Table}, the underlying data appears to be corrupt. Skipping this row and continuing backup; the affected database row should be inspected and fixed manually", entityType.SourceName);
+                                                _logger.LogError(ex, "Could not read next entity of type {Table}, the underlying data appears to be corrupt. Skipping this row and continuing backup; the affected database row should be inspected and fixed manually", entityType.SourceName);
                                                continue;
                                            }