magus v0.4.3 is out. See what's new
¶ View markdown source · ✎ Suggest an edit
1 min read

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.

[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, 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

MGS9024apinot found404
Last updated (8b20a199)
Earlier changes on this page (1)

Full history ↗ · Blame source ↗

Glossary

Server

The background process a person starts with magus server start. It serves MCP, the console, background jobs and the warm knowledge graph, and adopts nested magus calls into one pool. See server.

Snapshot

A point-in-time view of live state (the pool's occupancy or a tick of exported metrics), as opposed to accumulated history. See server.

Attention request

A durable "an agent is blocked" record, opened when a magus session notify event carries the waiting or permission outcome and held until a person disposes it. magus session attention lists what is open. Nothing closes one on its own; see doctrine.

Conventions

This page uses none of the site's convention markers. The full set is on the conventions page.