Record not archived

Type: https://plotdr.ch/problems/not-archived
HTTP status: 409
Content type: application/problem+json

What it means

Purging erases a record permanently, on request: a purged plot is deleted together with every check that references it, and a purged supplier together with every plot and check under it. PlotDR only purges a record that has already been archived, so an active record cannot be erased by a single request. Nothing was deleted.

This problem comes from POST /v1/plots/{plot_id}/purge and POST /v1/suppliers/{supplier_id}/purge. Both are reserved for a signed-in organization admin: an API key receives 403 from them before this check runs, so an integration never sees this problem.

Typical causes

The plot or supplier has not been archived yet.
The ID refers to a different, still active record than the one you archived.

What to do

Archive the record first, with DELETE /v1/plots/{plot_id} or DELETE /v1/suppliers/{supplier_id}, then purge it.

Purging cannot be undone. If you only want a record out of your lists, archiving it is enough.

Examples

POST /v1/plots/{plot_id}/purge on a plot that is still active.

{
  "type": "https://plotdr.ch/problems/not-archived",
  "title": "Record not archived",
  "status": 409,
  "detail": "plot must be archived before it can be purged",
  "instance": "/v1/plots/8e2d4c1a-5b7f-4e39-a0c6-1d9f2b7e3a54/purge"
}

POST /v1/suppliers/{supplier_id}/purge on a supplier that is still active.

{
  "type": "https://plotdr.ch/problems/not-archived",
  "title": "Record not archived",
  "status": 409,
  "detail": "supplier must be archived before it can be purged",
  "instance": "/v1/suppliers/2b6a9f3e-7c41-4d08-b5e2-9a3c1f6d8e70/purge"
}

See also: all problem types, theerror handling guide, and theAPI reference.