---
title: "MGS9024: resource not found"
description: A request named something the server holds no record of, such as an attention request, a figure or a path outside the reviewed patch. Answered 404.
tags: [MGS9024, api, not found, "404"]
---

# MGS9024: resource not found

The server answered `404 not found` because the route exists and the request
was well formed, but the thing it names is not there.

```text
[MGS9024] no attention request matches att-000000000000
  see: .../MGS9024.md
```

## Why

The route looked the name up and found nothing. Typical cases:

- **An attention request** already gone from the store, or never raised in this
  repository.
- **A figure** id the server does not draw.
- **A context path** that is not part of the reviewed patch, or a file no longer
  in the working tree.

A name that could be several things is [MGS9023](MGS9023.md), not this.

## Resolution

Re-read the listing the id came from (`GET /api/v1/attention`,
`GET /api/v1/diagrams`, `GET /api/v1/diff`) and use an id it names now.

## What this is not

- **Not a stale snapshot.** A review context read against a diff that has moved
  is [MGS9025](MGS9025.md).
- **Not a withheld console file.** That is [MGS9010](MGS9010.md).
- **Not an unknown token.** That is [MGS9006](MGS9006.md).