type URI on every subject_not_supported problem body: https://docs.get-exo.com/errors/subject_not_supported.
HTTP status: 400 Bad Request.
Why it happens
The brain family, the coding-session ingestion family andPOST /v1/purge scope by the credential’s own user rather than by a selector. Accepting the header there and ignoring it would read from, or write to, the wrong partition.
Exo refuses rather than ignores, so a mistake surfaces at the call instead of as mysteriously wrong data later.
How to fix it
- Remove the header on these routes.
- To act for a provisioned subject, use a subject-aware route. Retrieval, search, ingest, recall, graph, condition, settings and export creation all run the subject seam.
Related
subject_not_provisioned- Errors for the envelope and the full catalogue