type URI on every purge_impact_changed problem body: https://docs.get-exo.com/errors/purge_impact_changed.
HTTP status: 409 Conflict.
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_invalidsubject_mapping_invalid- Errors for the envelope and the full catalogue