---
title: "Restore a dismissed finding"
method: POST
path: "/projects/{projectId}/user-testing/scenarios/{scenarioId}/findings/{findingId}/undismiss"
tags: ["User testing"]
---

# Restore a dismissed finding

`POST /projects/{projectId}/user-testing/scenarios/{scenarioId}/findings/{findingId}/undismiss`

Undoes a dismissal. Bodyless: the path names the finding.

## Response `200`

The finding's new state.

- ScenarioFindingDismissed
  - `id` string, required
  - `scenarioId` string, required
  - `projectId` string, required
  - `dismissed` boolean, required — True from `/dismiss`, false from `/undismiss`. Dismissal is keyed on the finding's stable remediation id, so the same problem stays dismissed across regenerations.

## Other responses

- `401` — Missing, invalid, revoked, or orphaned key (`UNAUTHORIZED`) — or the **target MCP server** needs an OAuth grant (`OAUTH_REQUIRED`), which is a property of the server, not your key.
- `403` — Key is valid but not allowed to do this.
- `404` — Unknown project, server, or resource.
- `429` — Per-key rate limit exceeded (60 requests/minute sustained, bursts up to 10). Honor `Retry-After` and back off with jitter.
- `500` — Something failed on MCPJam's side.

---

[API](https://skmtc.net/mcpjam/apis/mcpjam-api.md) · [All operations](https://skmtc.net/mcpjam/apis/mcpjam-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/mcpjam/mcpjam-api/revisions/d62a29ba6e70/schema)