---
title: "MGS9027: internal failure"
description: The server failed to read its own state or build an answer. The body names the step that failed and never the cause, which is in the server log. Answered 500.
tags: [MGS9027, api, internal, "500"]
---

# MGS9027: internal failure

The server answered `500 internal` because a step it owns failed after the
request was accepted.

```text
[MGS9027] target graph failed
  see: .../MGS9027.md
```

## Why

The message names the step (`attention`, `target graph`, `graph build`,
`render`, a `diff` read) and nothing else. The underlying error can carry the
server's absolute paths, so it goes to the server log and never to the client.

## Resolution

Read the server's log output for the line with the same step name and the
request path. A failure that repeats for every request usually means the
workspace state on disk is unreadable; fix that and retry.

## What this is not

- **Not a bad request.** A change to the request fixes [MGS9023](MGS9023.md);
  it cannot fix this.
- **Not a missing workspace.** That is [MGS9026](MGS9026.md).