Start free →

Error codes

Azoth’s team tools

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

All error codes

platform_admin_required

What it means
This tool is for Azoth’s team only.
Most frequent cause
An account that is not on Azoth’s staff list.
What to do
Nothing to do on your side: this tool is not part of a workspace.
Who can do it
Azoth, or the operator of this deployment

staff_mfa_required

What it means
Azoth’s staff reach these tools only with two-factor authentication on the session.
Most frequent cause
A staff account signed in without its second factor.
What to do
Sign in again with your second factor, then try again.
Who can do it
Azoth, or the operator of this deployment

staff_access_unsealed

What it means
The staff access could not be sealed in the platform journal, so it was refused: no staff access goes unrecorded.
Most frequent cause
A brief database problem.
What to do
Try again in a moment; if it keeps failing, check the platform journal.
Who can do it
Azoth, or the operator of this deployment

override_expired

What it means
This contract override has ended: limits saved on it would not apply.
Most frequent cause
Its end date has passed.
What to do
Send a new end date in the future — or none — to put it back in force, or delete it.
Who can do it
Azoth, or the operator of this deployment

report_altered

What it means
The drill report does not match its sha256, so it was not recorded.
Most frequent cause
The report changed after its hash was computed.
What to do
Send the report exactly as it was hashed, with its sha256.
Who can do it
Azoth, or the operator of this deployment

catalog_not_here

What it means
The model catalogue is edited on Azoth’s service only; a deployment of your own imports it, signed, and Azoth’s service imports none.
Most frequent cause
An edit asked of a deployment of your own, or an import asked of Azoth’s service.
What to do
Edit prices on Azoth’s service; on a deployment of your own, import the signed catalogue.
Who can do it
Azoth, or the operator of this deployment

catalog_check_required

What it means
A catalogue entry is added only once it was checked against its source, today.
Most frequent cause
The check left unticked.
What to do
Check the price against its source, tick the check, then add the entry.
Who can do it
Azoth, or the operator of this deployment

catalog_source_required

What it means
A checked price names its source.
Most frequent cause
The source address left empty.
What to do
Give the address of the page the price comes from.
Who can do it
Azoth, or the operator of this deployment

catalog_draft_too_large

What it means
The draft file is larger than a draft may be.
Most frequent cause
Too many entries in one file.
What to do
Split the draft into smaller files.
Who can do it
Azoth, or the operator of this deployment

catalog_no_draft

What it means
No catalogue draft is open.
Most frequent cause
The draft was published or discarded in the meantime.
What to do
Open a draft, then make the change.
Who can do it
Azoth, or the operator of this deployment

catalog_draft_changed

What it means
The draft changed after it was reviewed, so it was not published.
Most frequent cause
Someone edited the draft after the review.
What to do
Review the draft again, then publish it.
Who can do it
Azoth, or the operator of this deployment

catalog_empty

What it means
An empty catalogue is never published.
Most frequent cause
A draft with no entry.
What to do
Add the entries, then publish.
Who can do it
Azoth, or the operator of this deployment

catalog_no_version

What it means
No version of the catalogue is in force to compare the draft with.
Most frequent cause
Nothing published yet on this deployment.
What to do
Publish a first version, then import drafts against it.
Who can do it
Azoth, or the operator of this deployment

catalog_import_concurrent

What it means
Another import of these proposals ran at the same time.
Most frequent cause
Two imports started together.
What to do
Import the file again.
Who can do it
Azoth, or the operator of this deployment

catalog_proposal_not_open

What it means
This proposal is no longer open.
Most frequent cause
Someone handled it a moment ago.
What to do
Reload the proposals.
Who can do it
Azoth, or the operator of this deployment

catalog_proposal_no_entry

What it means
This proposal holds no entry to add.
Most frequent cause
A proposal without a price.
What to do
Enter its price in the form.
Who can do it
Azoth, or the operator of this deployment

catalog_signature_invalid

What it means
The catalogue’s signature does not verify with the keys this deployment pins, so nothing was imported.
Most frequent cause
A catalogue signed with another key, or changed after it was signed.
What to do
Import a catalogue signed by Azoth, and check that this deployment runs a current version.
Who can do it
Azoth, or the operator of this deployment

catalog_hash_mismatch

What it means
A stored version of the catalogue does not hash to its recorded sha256, so it is neither served nor signed.
Most frequent cause
A published version changed after it was published.
What to do
Stop and investigate: a published version never changes.
Who can do it
Azoth, or the operator of this deployment

catalog_already_signed

What it means
This version of the catalogue is already signed: a signature is added once.
Most frequent cause
A second signature sent for the same version.
What to do
Nothing to do: the version keeps its signature.
Who can do it
Azoth, or the operator of this deployment

catalog_version_conflict

What it means
This deployment holds another version under that number, so the import was refused.
Most frequent cause
Two catalogues published under one number.
What to do
Find out which version this deployment holds before importing.
Who can do it
Azoth, or the operator of this deployment

breach_no_recipient

What it means
The workspaces named have no owner or admin to notify, so nothing was sent.
Most frequent cause
Workspaces without an owner or admin.
What to do
Write to the customer’s contact by hand.
Who can do it
Azoth, or the operator of this deployment

breach_notice_conflict

What it means
This notice number was already sent with other texts.
Most frequent cause
A notice changed after it was sent.
What to do
Send a follow-up under the next number.
Who can do it
Azoth, or the operator of this deployment

breach_recipients_truncated

What it means
Too many memberships to read at once, so nothing was sent.
Most frequent cause
A customer with very many members.
What to do
Send the notice for fewer workspaces at a time.
Who can do it
Azoth, or the operator of this deployment

breach_workspace_not_found

What it means
A workspace named does not exist, so nothing was sent.
Most frequent cause
A mistyped workspace id.
What to do
Check the workspace ids, then send again.
Who can do it
Azoth, or the operator of this deployment

breach_workspaces_not_one_customer

What it means
One notice concerns one customer: the workspaces named belong to several.
Most frequent cause
Workspaces of several organisations named together.
What to do
Send one notice per customer: one workspace, or the workspaces of one organisation.
Who can do it
Azoth, or the operator of this deployment

subprocessor_notice_conflict

What it means
This version was already announced with another content.
Most frequent cause
An announcement changed after it was sent.
What to do
Publish the change as a new version.
Who can do it
Azoth, or the operator of this deployment

subprocessor_notice_saas_only

What it means
Outside Azoth’s service, the deployment’s operator informs its own customers.
Most frequent cause
A deployment of your own.
What to do
Nothing to send from this deployment.
Who can do it
Azoth, or the operator of this deployment

subprocessor_notice_unsealed

What it means
The announcement could not be sealed, so nothing was sent.
Most frequent cause
A brief database problem.
What to do
Try again in a moment.
Who can do it
Azoth, or the operator of this deployment

subprocessor_recipients_truncated

What it means
Too many memberships to read at once, so nothing was sent.
Most frequent cause
Very many members to inform.
What to do
Try again later; if it keeps failing, have the reading raised.
Who can do it
Azoth, or the operator of this deployment