> ## 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.

# Purge impact changed

> The data changed between the dry run and the confirmation, so the confirm token no longer describes the deletion.

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

**HTTP status: `409` Conflict**.

```json theme={"theme":{"light":"github-light-default","dark":"github-dark-default"}}
{
  "type": "https://docs.get-exo.com/errors/purge_impact_changed",
  "title": "Purge impact changed",
  "status": 409,
  "detail": "The impact changed since the dry run, or the mapping is corrupt.",
  "code": "purge_impact_changed",
  "requestId": "req_9f2c41ab7d0e5c18"
}
```

## Why it happens

The dry run returns exact per-table impact counts and mints a token bound to them. The confirm re-counts before deleting and refuses if the numbers moved.

This is the whole safety property of the ceremony: you can never confirm a deletion larger than the one you reviewed.

## How to fix it

* Run the dry run again with `dryRun: true`, review the new counts, and confirm with the new token.
* If the counts keep moving, pause the ingestion writing into that partition first.

## Related

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