All Messages view no longer disabled during slow queries

[ramonsmits]

Stacked on:

• Fire a single audit query per query-control change #3104

Five fixes that make the All Messages view behave when queries are slow (large audit stores):

• Actionable feedback on failure: a failed or timed-out query showed a silent empty list (the error died as an unhandled watcher rejection). It now shows an alert explaining the instance might be too busy, with concrete suggestions. Pairs with the server-side query time limit in Terminate message queries that exceed a configurable time limit ServiceControl#5848.
• Controls never lock: the filter inputs were disabled while a query ran — causing the type-one-character-lose-focus bug and locking users out for the duration of a slow query. Entering a new query is now always possible.
• New queries supersede in-flight ones: starting a query aborts the one still running (the abort propagates through ServiceControl and terminates the database-side query) instead of silently dropping the new request; a superseded response can no longer overwrite newer results.
• Auto-refresh cooperates with slow queries: a tick landing mid-query no longer disappears and does not cancel the running query — it refreshes as soon as the results are in. A countdown bar shows when the next refresh is due.
• Typed searches always start: a search entered while the initial query was still running was silently ignored.
• Existing results stay visible and usable while a re-fetch runs: since Messages view does not indicate that it is waiting for a response from ServiceControl #3047 every re-fetch covered the list with a white overlay, which flashed on every auto-refresh tick and made the rows unreachable while waiting. That overlay existed because nothing could cancel a running query at the time; with cancel and supersede in place the refresh button is the only activity indicator, and the plain spinner remains only when there is nothing to show yet.
• Leaving the view stops its activity: navigating away aborts the in-flight query and releases the auto-refresh registration. It also clears the results: the rows live in the store, which outlives the view, so re-entering it used to show the previous visit's rows under the first-load spinner. A refresh in place keeps stale rows; coming back with possibly different inputs starts from a clean list.

Related:

• Terminate message queries that exceed a configurable time limit ServiceControl#5848

[johnsimons]

@ramonsmits I noticed that there is some extra repainting going on. It seems to redraw the whole screen.
Here is a comparison of the before (left) and after (right), using both Chrome and Safari.

Sep-07-2026.17-26-35.mp4

But overall looks good, although I am not sure about the countdown progress bar. I think I would prefer a text, and quite possible that would also be better for screen reader if we do efven support them!

[ramonsmits]

@ramonsmits I noticed that there is some extra repainting going on. It seems to redraw the whole screen. Here is a comparison of the before (left) and after (right), using both Chrome and Safari.

Good find ♥️! Interesting.. that needs a bit of digging :-)

although I am not sure about the countdown progress bar. I think I would prefer a text, and quite possible that would also be better for screen reader if we do even support them!

True, that bar isn't there anymore. It is now an animation within the refresh button.

However, due to the stacked PRs that isn't visible here.

[johnsimons]

I am approving this becasue I know quite a few other changes have been done in the next PRs