Resolve signals

Marks each signal in signalIds as resolved, archiving it and re-enabling its notifications. Unless keepMonitoring is false, linked evaluations keep running so a new occurrence reopens the signal as regressed.

post/v1/projects/{projectSlug}/signals/resolve

Path parameters

projectSlugstring required

Project slug (human-readable identifier)

Request body

signalIdsstring[] required

Non-empty list of signal ids. Operations are idempotent — already-applied signals are unchanged.

keepMonitoringboolean

Whether linked evaluations keep running after the resolve, so regressions are detected. Defaults to the project setting.

Response

Per-signal result

Changes

Changed in 3 of the 67 revisions of this API.12

Jul 21, 2026a74967b6b9721See the full diff
- ○
  endpoint added
  endpoint-added
Jun 28, 20265cedc15b21b51See the full diff
- ▲
  api path removed without deprecation
  api-path-removed-without-deprecation
This revision also has 9 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
Jun 18, 202694100174a89b1See the full diff
- ○
  endpoint added
  endpoint-added
This revision also has 22 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

Full history