From e6db2b4d6a4d84e674dc0691d9b3189e25bb43b7 Mon Sep 17 00:00:00 2001
From: Scott Idem
Date: Thu, 21 May 2026 12:30:53 -0400
Subject: [PATCH] fix(idaa): add Clear Cache & Reload escape hatch to recovery
meetings server error state
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
"Try Again" resets auto_retry_count but reuses the same localStorage state — if
ae_loc or ae_idaa_loc holds a stale account_id or api_secret_key, every retry
fails identically and the user is stuck in an infinite error loop.
New button clears ae_loc + ae_idaa_loc from localStorage and db_events.event
from IDB, then reloads via the sessionStorage-preserved UUID URL (same logic as
the IDAA layout's Clear Cache & Reload). Forces a fresh FQDN handshake and
re-derives correct auth state. Guidance text shown so users know to try it when
Try Again keeps failing.
Co-Authored-By: Claude Sonnet 4.6
---
.../(idaa)/recovery_meetings/+page.svelte | 45 ++++++++++++++-----
1 file changed, 35 insertions(+), 10 deletions(-)
diff --git a/src/routes/idaa/(idaa)/recovery_meetings/+page.svelte b/src/routes/idaa/(idaa)/recovery_meetings/+page.svelte
index e07365c5..c1d78948 100644
--- a/src/routes/idaa/(idaa)/recovery_meetings/+page.svelte
+++ b/src/routes/idaa/(idaa)/recovery_meetings/+page.svelte
@@ -484,16 +484,41 @@ if (browser) {
Unable to load meetings — server error. Please try again.
{/if}
-
+
+ If "Try Again" keeps failing, use "Clear Cache & Reload" to reset your local data.
+