Start free →

Error codes

Support: tickets and access

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

All error codes

ticket_contains_secret

What it means
The message holds what looks like a secret — an API key, a password, a token — so it was not sent.
Most frequent cause
A key or a credential pasted into the message.
What to do
Remove the secret from the message, then send it again: support never needs a key.
Who can do it
Any member of the workspace · Open the screen

transcript_contains_secret

What it means
The assistant conversation joined to the ticket holds what looks like a secret, so the ticket was not created.
Most frequent cause
A key or a credential typed during the conversation.
What to do
Create the ticket again without joining the conversation.
Who can do it
Any member of the workspace · Open the screen

ticket_closed

What it means
This ticket is closed: it takes no more replies.
Most frequent cause
It was closed after it was resolved.
What to do
Open a new ticket and name this one in it.
Who can do it
Any member of the workspace · Open the screen

ticket_not_resolved

What it means
Only a ticket marked resolved asks whether it was solved.
Most frequent cause
The ticket was reopened or closed in the meantime.
What to do
Reload the ticket to see its status.
Who can do it
Any member of the workspace · Open the screen

cause_required

What it means
A ticket is resolved or closed only with its cause.
Most frequent cause
No cause chosen for the ticket.
What to do
Choose the ticket’s cause, then resolve or close it.
Who can do it
Azoth, or the operator of this deployment

critical_requires_incident

What it means
Only an incident ticket can be critical.
Most frequent cause
The critical severity chosen for a question or a request.
What to do
Set the ticket’s category to incident, or lower its severity.
Who can do it
Azoth, or the operator of this deployment

support_unavailable

What it means
The support data could not be read, so nothing was done.
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

support_access_saas_only

What it means
Access by Azoth’s support exists only on Azoth’s service: a deployment of your own has none.
Most frequent cause
This deployment is not Azoth’s service.
What to do
Nothing to grant: your deployment’s operator reaches its data directly.
Who can do it
Azoth, or the operator of this deployment

support_access_open

What it means
A support access to this workspace is already waiting for a decision, or open.
Most frequent cause
A request was already made.
What to do
Decide or close the access already there, in Settings › Access.
Who can do it
An owner of the workspace · Open the screen

support_access_unsealed

What it means
The support access could not be sealed in the journals, so it was refused: no access goes unrecorded.
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

grant_not_pending

What it means
This request for support access was decided already.
Most frequent cause
Another owner decided it a moment ago, or it lapsed.
What to do
Reload Settings › Access to see its state.
Who can do it
An owner of the workspace · Open the screen

grant_not_active

What it means
This support access is no longer open.
Most frequent cause
It ended, or was closed a moment ago.
What to do
Reload Settings › Access to see its state: opening access again takes a new request.
Who can do it
An owner of the workspace · Open the screen

emergency_requires_enterprise

What it means
Emergency access by Azoth’s support is part of the Enterprise plan.
Most frequent cause
The workspace is not on the Enterprise plan.
What to do
Ask our team about Enterprise, or grant support access request by request in Settings › Access.
Who can do it
An owner of the workspace · Open the screen

emergency_not_consented

What it means
The workspace’s owners have not agreed to emergency access, so none can be opened.
Most frequent cause
Emergency access is off in the workspace’s support settings.
What to do
Ask for access through an ordinary request, which an owner decides in Settings › Access.
Who can do it
Azoth, or the operator of this deployment

emergency_requires_critical

What it means
Emergency access is opened only for a critical ticket.
Most frequent cause
The ticket is not of critical severity.
What to do
Use an ordinary access request, which an owner decides.
Who can do it
Azoth, or the operator of this deployment

second_staff_required

What it means
An emergency access is confirmed by a second member of Azoth’s staff, never by the one who asked for it.
Most frequent cause
The person who requested it tried to confirm it.
What to do
Ask another member of the staff to confirm the access.
Who can do it
Azoth, or the operator of this deployment