From 63c7d88bd27f4035b1b5837b5d526df83faba0a2 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=C3=89mile=20R=C3=A9?= Date: Wed, 15 Jul 2026 09:25:04 +0200 Subject: [PATCH] Catch recent-updates row errors at the section MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The recent-updates rows all come from a single connection query, so a per-row boundary isolated a failure that the rows actually share and left an unrecoverable row (its retry only re-read the same errored store). Let a row's field error bubble to the section boundary instead, so the whole list degrades and recovers as one unit. Signed-off-by: Émile Ré --- .../RecentUpdates/RecentUpdatesSection.tsx | 20 ++++--------------- 1 file changed, 4 insertions(+), 16 deletions(-) diff --git a/apps/compliance-portal/src/components/RecentUpdates/RecentUpdatesSection.tsx b/apps/compliance-portal/src/components/RecentUpdates/RecentUpdatesSection.tsx index 334f0a504..f01a45c7f 100644 --- a/apps/compliance-portal/src/components/RecentUpdates/RecentUpdatesSection.tsx +++ b/apps/compliance-portal/src/components/RecentUpdates/RecentUpdatesSection.tsx @@ -94,22 +94,10 @@ function RecentUpdatesSectionContent({ trustCenterKey }: RecentUpdatesSectionPro
{updates.map(update => ( - // A single failing row degrades to a compact horizontal inline error. - ( -
- -
- )} - > - -
+ // Rows share fate (one connection query), so a row's field error + // bubbles to the section boundary above rather than degrading a + // single, unrecoverable row. + ))}