---
url: /errors/subscriber_already_erased.md
---
# `subscriber_already_erased`

`subscriber_already_erased`

## Description

The subscriber's DEK has already been destroyed. GDPR enforcement will neither
return nor provision another key because that would reverse crypto-shredding.

## HTTP Status

`422 Unprocessable Entity`

## `doc_url` Format

The `doc_url` value is an absolute URL and changes by environment:

`<docs-base-url>/errors/subscriber_already_erased`

## Typical Causes

* A consuming context attempted to fetch a DEK after erasure.
* A creating context retried provisioning after the subscriber had been erased.

## How To Fix

1. Stop processing or persisting personal data for the subscriber.
2. Do not retry DEK provisioning for that subscriber.
3. Preserve the erased state in the calling workflow.