Skip to content

Show the actual JSON the API returns for a refused delete #154

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mastacontrola merged 1 commit into from
Aug 29, 2026
Merged

Show the actual JSON the API returns for a refused delete #154

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 9 additions & 4 deletions docs/kb/reference/referential-integrity.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -134,10 +134,15 @@ changed** — a refused delete leaves the record and everything pointing at it
exactly as they were.

Over the API the same message comes back as **HTTP 409 Conflict**, with the
sentence as the response body. 409 rather than a generic error is
deliberate: it means the request itself was fine and will work once the
blocking record is dealt with, so a script can tell "fix this and retry"
apart from "this request was wrong".
sentence under `error` in the response body:

```json
{"error": "Cannot delete this storage group because a location still refers to it. Reassign or remove it first."}
```

409 rather than a generic error is deliberate: it means the request itself
was fine and will work once the blocking record is dealt with, so a script
can tell "fix this and retry" apart from "this request was wrong".

>[!note]
>Occasionally the message is the database's own instead:
Expand Down