Skip to content

purge_not_applicable

The API answers purge_not_applicable in the code field of its error envelope.

  • HTTP status: 422 Unprocessable Content.
  • Fault: customer. Something in the request, or on your side (a credential, a setting, the data), needs to change before it can succeed.

That table is kept in history mode or append-only, whose rows are never purged: a history table’s closed versions are its history, and an append-only table is a log. Nothing was changed.

Every error carries code, message (for your logs, in English), fault, request_id and docs (this page). Quote the request_id when you ask about a particular request. See all error codes.