diff --git a/04-ISSUES/353-the-controller-asked-before-the-bus-held-its-grant/00-report.md b/04-ISSUES/353-the-controller-asked-before-the-bus-held-its-grant/00-report.md
index 0bff1898..f1e81cc9 100644
--- a/04-ISSUES/353-the-controller-asked-before-the-bus-held-its-grant/00-report.md
+++ b/04-ISSUES/353-the-controller-asked-before-the-bus-held-its-grant/00-report.md
@@ -25,8 +25,10 @@ On 2026-10-09, local times on the control node, from its controller's journal (o
   it in place (the same second the watchdogs saw "jetstream not enabled", the reload's moment); 17:56:10 the
   same connection asked successfully, and again at 18:03:53. The server applies a reloaded permission to a
   standing connection: no reconnect was needed or made.
-- The condition stays open for an hour after the last refusal (the bus-advisory signal's quiet time) and
-  clears by itself.
+- `bus.controller.refused` was raised at 17:54:06 and cleared by itself at 18:11:44, about 15 minutes after
+  the last refusal at 17:56:05 (the controller's condition history). The condition's evidence lists the same
+  refusal read again every 30 seconds until 18:10:35; the journal shows no refusal after 17:56:05, so those
+  are the signal reading its record again, not new refusals.
 
 ## Why it is an issue