fix(webapp): no watch offer on a paused queue, in the button or the chips

A paused queue can neither drain nor grow, so every condition it could watch for is a promise nothing keeps until someone resumes it.

Author: kathiekiwi

apps/webapp/app/components/dashboard-agent/suggested-prompts/page-mappers.test.ts

@@ -244,6 +244,16 @@ describe("queueAgentPageContext", () => {
     expect(context?.signals).toEqual([]);
   });
 
+  it("offers no watch on a paused queue, even when it is at capacity", () => {
+    // Paused and saturated at once: nothing will drain or grow until it is resumed, so a
+    // watch would promise an answer that can't come.
+    const context = queueAgentPageContext(
+      queueLoaderData({ paused: true, running: 10, queued: 40, concurrencyLimit: 10 })
+    );
+
+    expect(context?.signals).toEqual([]);
+  });
+
   it("emits nothing for an unlimited queue, however deep the backlog", () => {
     const context = queueAgentPageContext(
       queueLoaderData({ concurrencyLimit: null, running: 99, queued: 99 })

apps/webapp/app/components/dashboard-agent/suggested-prompts/page-mappers.ts

@@ -210,7 +210,8 @@ export function queueAgentPageContext(data: unknown): AgentPageContext | undefin
   const health = atCapacity ? "crit" : paused || queued > 0 || waitingTooLong ? "warn" : "ok";
 
   const signals: AgentPageSignal[] = [];
-  if (atCapacity) {
+  // Nothing to watch on a paused queue: it can neither drain nor grow until it is resumed.
+  if (atCapacity && !paused) {
     // A backlog at least as deep as the limit won't clear this cycle.
     signals.push({ kind: "concurrency_saturation", severity: queued >= limit! ? "crit" : "warn" });
   }

apps/webapp/app/routes/_app.orgs.$organizationSlug.projects.$projectParam.env.$envParam.queues_.$queueParam/route.tsx

@@ -342,7 +342,11 @@ export default function Page() {
                 tooltip="Ask why this queue is backed up"
               />
             ) : null}
-            <WatchButton spec={queueWatchRecommendation(queue.name, { oldestWaitMs })} />
+            {/* A paused queue can't drain or grow, so every watch it could offer is a
+                promise nothing will keep until someone resumes it. */}
+            {queue.paused ? null : (
+              <WatchButton spec={queueWatchRecommendation(queue.name, { oldestWaitMs })} />
+            )}
             <QueueOverrideConcurrencyButton
               queue={queue}
               environmentConcurrencyLimit={environmentConcurrencyLimit}

internal-packages/dashboard-agent/GUIDEBOOK.md

@@ -82,7 +82,7 @@ Two separate mechanisms, decided differently — worth knowing before a demo.
 | Page | Button | Shown when |
 | --- | --- | --- |
 | Queue | Investigate | the queue is degraded: not paused, and either `running >= concurrencyLimit` with a non-empty queue, or the oldest run has waited >= 5 min |
-| Queue | Watch… | always |
+| Queue | Watch… | unless the queue is paused — a paused queue can neither drain nor grow |
 | Error group | Investigate this error | always |
 | Error group | Watch… | always |
 | Run (span panel) | Watch… | while the run is not in a final status |
@@ -104,7 +104,9 @@ page's live signals — a different decision from the buttons above:
 | `concurrency_saturation` | watch |
 
 A backed-up queue therefore offers "tell me when the backlog drains", never
-"investigate" — the page's own Investigate button is the one that asks that.
+"investigate" — the page's own Investigate button is the one that asks that. A
+paused queue offers neither: `concurrency_saturation` is withheld while it is
+paused, for the same reason the button is.
 
 ---