type URI on every subject_mapping_invalid problem body: https://docs.get-exo.com/errors/subject_mapping_invalid.
HTTP status: 409 Conflict.
Why it happens
Erasing a subject deletes tenant rows, the mapping and the internal user. Before touching anything, Exo checks that the mapping points at a service user, which is what a provisioned subject always is. If it does not, the operation aborts before a single row is removed. A partial erasure is worse than a refused one.How to fix it
- Do not retry: the state will not change on its own.
- Quote the
requestIdand the subject id when you report it. This indicates a mapping that needs repair rather than a client mistake.
Related
subject_not_foundconflict- Errors for the envelope and the full catalogue