Dismissing a signal that's wrong
Last updated on
Agents and syncs sometimes get it wrong: a test ticket trips an SLA breach, a dip is just seasonal, a champion "went quiet" on holiday. Expand the signal and click Dismiss to say it isn't real. Add a one-line reason, or skip it.
| Resolved | Dismissed | |
|---|---|---|
| Means | real, and handled | never real |
| Set by | syncs and re-checks, automatically | you, by hand |
| Raised again later? | yes, if it recurs | not for a while (below) |
What dismissing does
- Removes it from the account's main list (it stays under the Dismissed filter) and the Signals dashboard.
- Dismisses its open tasks too, each with the note "Dismissed with its signal", and notifies their assignees. Undo brings them back.
- Stops it counting against health on the next recompute.
- Keeps it out of dashboards, the Portfolio Digest and what agents read.
- Stops it being raised again: integration signals (one specific ticket or invoice) are suppressed permanently; agent and workflow signals for 30 days, because they describe a condition that can genuinely return.
Dismissing many at once
On Dashboards → Signals, tick the rows (or Select all) and click Dismiss. The same rules apply to each one, and the result says how many were dismissed and why any were skipped (for example, already dismissed).
Undoing it
The confirmation toast has Undo. Later, click Dismissed on Dashboards → Signals to see who dismissed what and why, each with Restore. Every dismissal and restore is audit-logged.
Tip
Dismissing needs the signals.dismiss permission, which CSMs have by default.