---
title: "MGS9025: request conflicts with current state"
description: A well-formed request contradicted the state it addresses, such as an attention request already closed, a review snapshot gone stale, or no review session attached yet. Answered 409.
tags: [MGS9025, api, conflict, state, "409"]
---

# MGS9025: request conflicts with current state

The server answered `409 aborted` because the request was well formed and the
thing it names exists, but the request cannot apply to it as it now stands.

```text
[MGS9025] review snapshot is stale; refresh the diff
  see: .../MGS9025.md
```

## Why

The request was written against a state that is no longer the current one:

- **A request already closed.** An attention request someone else disposed of
  first; the message says who and when.
- **A stale snapshot.** File context asked against a diff digest the working
  tree has since moved past.
- **No review session attached.** A review op arrived before any
  `GET /api/v1/diff` paired a session to this workspace.
- **An import figure with no symbol index.** The figure would read as "nothing
  imports anything", so it is refused.

Retrying the same request cannot succeed until the state changes.

## Resolution

Read the current state and act on that: fetch the diff again, list the attention
queue, `GET /api/v1/diff` before the first review op, or run `magus graph build`
for the import figure.

## What this is not

- **Not a malformed request.** That is [MGS9023](MGS9023.md), fixed by changing
  the request.
- **Not a workspace that is loading.** That is
  [MGS3017](../sandbox/MGS3017.md) while it loads, retried after a moment.