processing_complexity_exceeded

HTTP status: 413 Content Too Large

What happened

The text needs more work than its length allows: more candidate matches or matched characters than the per-character bounds in /v1/access, coreference matching work beyond its per-character bound (for example one name nested inside itself thousands of times), or more time for the organisation rules than their limit, which grows with the text and the number of rules. The bounds grow with the text, so splitting it rarely helps. Nothing partial is returned.

What to do

Check the text for long repetitive patterns, or ask your organisation's administrator to simplify its rules. Splitting the text rarely helps.

A text job can also end with this code. The job's status then carries it in the field error.

Example

JSON

{
  "error": "processing_complexity_exceeded",
  "request_id": "0f8e2c4a-6b1d-4e3f-9a7c-5d2b8e1f4a60",
  "doc_url": "https://developers.komplai.dk/errors/processing_complexity_exceeded"
}

Every response carries a Request-Id header, and an error body repeats it as request_id. Quote it when you ask komplai about a call.

Endpoints that can return it

POST /v1/redact Pseudonymise a text
POST /v1/redact/file Pseudonymise the text of a PDF or Word file (beta)

All error codes