> ## Documentation Index
> Fetch the complete documentation index at: https://docs.get-exo.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Edge not found

> No such graph edge exists for the effective subject.

This page is the resolution target of the RFC 9457 `type` URI on every `edge_not_found` problem body: `https://docs.get-exo.com/errors/edge_not_found`.

**HTTP status: `404` Not Found**.

```json theme={"theme":{"light":"github-light-default","dark":"github-dark-default"}}
{
  "type": "https://docs.get-exo.com/errors/edge_not_found",
  "title": "Edge not found",
  "status": 404,
  "detail": "No such edge owned by the effective subject.",
  "code": "edge_not_found",
  "requestId": "req_9f2c41ab7d0e5c18"
}
```

## Why it happens

Edges are scoped like nodes. An edge belonging to another subject is not visible to this caller.

A removed edge is tombstoned and does not come back on a get.

## How to fix it

* Confirm the id came from `GET /v1/graph/edges` under the same effective subject.
* Re-assert the relation with `POST /v1/graph/edges` if it should exist.

## Related

* [`node_not_found`](/errors/node_not_found)
* [`not_found`](/errors/not_found)
* [Errors](/platform/errors) for the envelope and the full catalogue