Abuse Report Already Decided

abuse-report-not-pending · 409

An operator tried to decide an abuse report that was already resolved or dismissed, so nothing changed.

Only operators reach the routes that send it. reportId names the report. The report's state shows in detail only: the API writes the HTTP status into status over it.

Besides the members every error carries, this type adds reportId.

Common causes

  • Another operator decided it first.
  • The resolve or dismiss call was sent twice.

How to fix the call

  • Read the report to see how it was decided.
  • Don't retry: a decided report stays decided.

Example response

json
{
  "type": "abuse-report-not-pending",
  "title": "Abuse Report Already Decided",
  "detail": "This abuse report was already dismissed; it cannot be decided again.",
  "reportId": "0199e0a3-6f21-7c4a-9d18-2b7c5f3ad402",
  "status": 409,
  "requestId": "req-1785231000000-4f7b2c9ae",
  "timestamp": "2026-07-28T09:30:00.000Z",
  "path": "/v1/abuse/admin/reports/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad402/resolve",
  "method": "POST",
  "instance": "POST /v1/abuse/admin/reports/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad402/resolve",
  "docs": "https://ghaym.me/docs/errors/abuse-report-not-pending"
}