Start free →

Error codes

Proof: holds, dossiers and timestamps

Each code of this family: what it means, its most frequent cause, what to do and who can do it.

All error codes

subject_erasure_unavailable

What it means
The tool that erases a person's data is not ready on this deployment.
Most frequent cause
On Azoth’s service, an update not applied yet. On a deployment of your own, its operator has not applied the latest database updates.
What to do
Erasing a person's data needs a database update that is not applied yet. Contact your operator or Azoth's support.
Who can do it
Azoth, or the operator of this deployment

entries_not_found

What it means
Some of the decisions designated are not in the journal of this workspace.
Most frequent cause
A sequence number from another workspace, or a typo.
What to do
Some of these decisions are not in this workspace’s journal.
Who can do it
An owner of the workspace

decision_not_found

What it means
No sealed decision carries this reference.
Most frequent cause
A reference never sent in X-Azoth-Decision-Ref, or sent to another workspace.
What to do
No sealed decision carries this reference.
Who can do it
Any member of the workspace

too_many_entries

What it means
A hold designates 500 decisions at most.
Most frequent cause
A range or a reference that covers more decisions.
What to do
A hold designates 500 decisions at most.
Who can do it
An owner of the workspace

invalid_decision_ref

What it means
The decision reference is not in a form Azoth accepts.
Most frequent cause
An empty or malformed value.
What to do
This decision reference is not valid.
Who can do it
The developer of the calling code

hold_not_found

What it means
This litigation hold no longer exists.
Most frequent cause
A link from another workspace, or a hold id typed by hand.
What to do
This litigation hold no longer exists.
Who can do it
An owner of the workspace

hold_released

What it means
This hold is released already.
Most frequent cause
Its release was approved a moment ago.
What to do
This hold is already released.
Who can do it
An owner of the workspace

release_pending

What it means
A release of this hold is already waiting for a decision.
Most frequent cause
Someone asked for the release before you.
What to do
A release of this hold is already waiting for a decision.
Who can do it
An owner of the workspace

period_invalid

What it means
The period asked is not valid.
Most frequent cause
A start after its end, or a period longer than 400 days.
What to do
Choose a period of 400 days at most, its start before its end.
Who can do it
Any member of the workspace

timestamp_level_unavailable

What it means
This deployment cannot timestamp at the level chosen.
Most frequent cause
A level its operator has not set up, such as a local authority on the SaaS.
What to do
This deployment cannot timestamp at that level: ask its operator, or choose another level.
Who can do it
Azoth, or the operator of this deployment

dossier_signature_unavailable

What it means
The dossier was not exported: Azoth could not sign it with the workspace’s key, and it never hands over an unsigned dossier — nothing would bind its content to the workspace, so entries could be removed from it unnoticed.
Most frequent cause
The workspace’s signing key could not be read or made right now, or the journal’s head it must commit could not be read: a problem on the deployment’s side, not in your data. Outside SaaS, the deployment’s operator fixes it.
What to do
The dossier was not exported: it could not be signed with the workspace’s key, and an unsigned dossier cannot be trusted. Try again in a few minutes; if it persists, contact support.
Who can do it
Azoth, or the operator of this deployment

tsa_chain_required

What it means
A timestamp authority is saved only with its root certificates.
Most frequent cause
The certificate field was left empty.
What to do
Paste the root certificate(s) of the authority (PEM): a token is kept only when it chains to them.
Who can do it
An owner or admin of the workspace

tsa_url_invalid

What it means
The address of the authority is refused.
Most frequent cause
An address in http, or one on a private network.
What to do
The authority’s address must be an https URL on the public internet.
Who can do it
An owner or admin of the workspace

tsa_check_timeout

What it means
The authority did not answer the test request of Azoth in time.
Most frequent cause
An overloaded authority, or a firewall that drops the request.
What to do
The authority did not answer the test request in time. Nothing was saved.
Who can do it
An owner or admin of the workspace

tsa_check_unreachable

What it means
Azoth could not reach the authority.
Most frequent cause
A wrong address, a DNS problem, or a firewall.
What to do
The authority could not be reached. Nothing was saved.
Who can do it
An owner or admin of the workspace

tsa_check_http_error

What it means
The authority answered the test request with an HTTP error.
Most frequent cause
A wrong path in the address, or missing or wrong credentials.
What to do
The authority answered the test request with an error. Check its address and credentials. Nothing was saved.
Who can do it
An owner or admin of the workspace

tsa_check_refused

What it means
The authority refused to timestamp the test request.
Most frequent cause
Credentials or a policy the authority does not accept.
What to do
The authority refused the test request. Check its address, credentials and policy. Nothing was saved.
Who can do it
An owner or admin of the workspace

tsa_check_invalid_token

What it means
The authority answered, but its token does not chain to the root certificates given.
Most frequent cause
The wrong root certificate pasted, or an intermediate certificate missing.
What to do
The authority answered, but its token does not chain to the root certificates given. Nothing was saved.
Who can do it
An owner or admin of the workspace

tsa_check_failed

What it means
The authority could not be checked.
Most frequent cause
An answer Azoth could not read.
What to do
The authority could not be checked. Nothing was saved.
Who can do it
An owner or admin of the workspace

footprint_not_read

What it means
A repository’s AI footprint is attested only once it is turned on and read in full.
Most frequent cause
The footprint is off for the repository, or its reading has not finished.
What to do
Turn the footprint on for the repository, wait until its reading has finished, then attest it.
Who can do it
An owner or admin of the workspace

ai_footprint_statement_not_found

What it means
No sealed AI footprint statement of this workspace has this id.
Most frequent cause
A statement not sealed yet, or an id from another workspace.
What to do
Choose a sealed statement, or wait until it is sealed.
Who can do it
Any member of the workspace · Open the screen

unknown_framework

What it means
No compliance framework has this id.
Most frequent cause
A mistyped id, or a framework Azoth does not hold.
What to do
Choose a framework from the list in Proofs › Dossiers.
Who can do it
Any member of the workspace · Open the screen

unknown_requirement

What it means
This framework has no requirement with this id.
Most frequent cause
A mistyped id, or a requirement of another framework.
What to do
Choose the requirement from the framework’s own list.
Who can do it
An owner or admin of the workspace · Open the screen

already_declared

What it means
This requirement is already declared out of scope.
Most frequent cause
A second declaration of the same requirement.
What to do
Keep the declaration in force, or revoke it before declaring it again.
Who can do it
An owner or admin of the workspace · Open the screen