---
title: "MGS9026: server has no workspace"
description: A route that needs a workspace was served by a process started without one, so waiting will not help. Answered 503.
tags: [MGS9026, api, workspace, "503"]
---

# MGS9026: server has no workspace

The server answered `503 unavailable` because the route reads a workspace
(insight, the target plan, a diff) and this process holds none.

```text
[MGS9026] this server was started without a workspace
  see: .../MGS9026.md
```

## Why

A server can run without a workspace, serving only what needs none. The console
treats this answer as "render the empty state", which is why it is a `503` and
not a `500`. Unlike a workspace that is loading, nothing changes by waiting. A
review context read whose workspace root no longer resolves answers the same
way.

## Resolution

Restart the server from the workspace root: `magus server stop`, then
`magus server start`.

## What this is not

- **Not a workspace that is loading.** That is
  [MGS3017](../sandbox/MGS3017.md), and the same call succeeds after a moment.
- **Not a workspace that failed to load.** That is
  [MGS3016](../sandbox/MGS3016.md).