Skip to main content
Not every signal is a real problem. The first job on the Signals queue is triage: confirm the ones that matter and mute the ones that don’t.

​
The two states

  • Confirm — this is a real problem worth fixing. Signal is now eligible for promotion to an Improvement.
  • Mute — this is a false alarm or acceptable. Signal is closed. Similar future signals may auto-mute.
You can also defer — leave in new state to revisit later. Or edit — add notes, retag, adjust severity — before confirming.

​
The signal detail view

Click any signal to see:
  • The trace — click through to inspect the run.
  • The feedback — the user’s comment (if any), the categorization, the reference correction.
  • The context — what the Agent’s role is, what data sources it had, what tools it called.
  • The pattern — if the signal joined a cluster, other signals in the cluster.
  • Similar resolved signals — anything from the past that looked like this.

​
Triage in one click

For high-volume queues, the queue view has one-click buttons:
  • Confirm (checkmark).
  • Mute (X).
  • Defer (clock).
Keyboard shortcuts:
  • Y — confirm.
  • N — mute.
  • D — defer.
  • E — open editor.
  • ↓ / ↑ — next / prev.
Useful for going through 20-50 signals in a session.

​
Muting well

When you mute, add a reason. Reasons are the seed for auto-muting future noise:
  • “User feedback was sarcastic — answer was actually correct.”
  • “Verification false positive — graph missing an edge; will add later.”
  • “Test traffic from staging.”
Nora uses the reason + signal features to learn which future signals to auto-mute. You’ll see auto-muted signals in a separate view with the “auto-muted” tag — spot-check occasionally to make sure the learning is right.

​
Bulk operations

Select multiple signals (checkbox) then bulk-confirm or bulk-mute. Useful for:
  • Muting a batch of test traffic.
  • Confirming an entire cluster at once (see Clusters).

​
After confirming

Confirmed signals show up in the Improvements candidate list. From there, you can:
  • Promote to an Improvement immediately.
  • Wait until the signal is joined by more similar ones (turn confirmed signals into a cluster).
  • Ignore — confirmed signals that never get promoted just stay confirmed. They aren’t lost; they’re waiting.

​
Reopening a muted signal

Muted signals can be reopened for 30 days after muting. Beyond that, they close permanently. If a muted pattern turns out to be real, a fresh signal on the same pattern creates a new open signal.

​
Muting vs. suppressing a source

Muting is per-signal. If a specific source is systematically noisy for your Flow, turn it off entirely in Signals settings rather than muting each one.