fix(central-ui): notification deep link and relay use the stored N-form NotificationId

Notify.Send mints NotificationId as Guid "N" (no dashes) and the outbox parses it back into the audit row's CorrelationId, so the Flow Debugger's Notify node linked and relayed a "D" string the Notifications table never matches (found live: the report opened empty). The link and RetryNotificationRequest now use "N", and the Notification report normalises any Guid-shaped ?correlationId= to "N" so Audit Log and Flow Debugger callers both land. Claude-Session: https://claude.ai/code/session_01NcMG6xXdsJbmD2wYAgkK29
2026-09-06 11:16:24 -04:00
parent 1f8c5810ca
commit 91d14ebdee
6 changed files with 29 additions and 6 deletions
@@ -515,7 +515,9 @@
            var candidate = values.ToString()?.Trim();
            if (!string.IsNullOrEmpty(candidate) && candidate.Length <= MaxNotificationIdFilterLength)
            {
-                _notificationIdFilter = candidate;
+                // NotificationId is minted as a Guid in "N" form (no dashes); a caller that only has the
+                // audit row's CorrelationId (a Guid, usually rendered "D") must still land on the row.
+                _notificationIdFilter = Guid.TryParse(candidate, out var guid) ? guid.ToString("N") : candidate;
            }
        }
    }