Error codes
Any request: validation and server failures
Each code of this family: what it means, its most frequent cause, what to do and who can do it.
validation_failed
- What it means
- The request’s body or parameters do not match what the route accepts, so nothing was done. The answer’s
errordescribes the problem andfieldnames the field, when there is one. - Most frequent cause
- A required field missing, a value of the wrong type or out of its range, or an unknown option — often a client built against an older version of the API.
- What to do
- A value sent is not accepted. Correct the field it names, then send it again.
- Who can do it
- The developer of the calling code
internal_error
- What it means
- The request failed on Azoth’s side, for a reason the answer does not give: nothing in the request was at fault. The failure is recorded for Azoth’s team.
- Most frequent cause
- A brief database or network problem, or a bug.
- What to do
- Something failed on Azoth’s side. Try again in a moment; if it keeps failing, contact support.
- Who can do it
- Azoth, or the operator of this deployment
not_found
- What it means
- Nothing the request names exists in this workspace — or it exists, but this caller may not read it.
- Most frequent cause
- An id typed by hand or taken from another workspace, an item deleted since, or a request that another API key made.
- What to do
- Nothing with this id was found in this workspace: it may have been deleted, or belong to another workspace. Reload, or check the id.
- Who can do it
- Any member of the workspace
unknown_tool
- What it means
- No insight tool has this name. The answer’s
toolslists the names that exist. - Most frequent cause
- A mistyped name, or a former name whose transition period has ended.
- What to do
- No tool has this name: use one of the names the answer lists under tools.
- Who can do it
- The developer of the calling code
not_configured
- What it means
- This deployment lacks a setting the request needs — a secret, a vendor’s account or keys — so nothing was done. Trying again changes nothing until it is set.
- Most frequent cause
- On Azoth’s service, a configuration fault Azoth’s team fixes. On a deployment of your own, a setting its operator has not set; the server’s log names it.
- What to do
- This feature is not set up on this deployment, and nothing was done. Contact support or the operator of this deployment: a setting it needs is missing.
- Who can do it
- Azoth, or the operator of this deployment
migration_missing
- What it means
- This feature needs a database update that is not applied yet, so nothing was done.
- 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
- This feature needs a database update that has not been applied yet, and nothing was done. Contact support or the operator of this deployment.
- Who can do it
- Azoth, or the operator of this deployment
action_not_offered
- What it means
- This action is not offered for this item of the queue.
- Most frequent cause
- A screen that showed an older state of the item.
- What to do
- Reload the queue, then choose one of the actions it offers.
- Who can do it
- Any member of the workspace · Open the screen
item_not_waiting
- What it means
- This item no longer waits in the queue.
- Most frequent cause
- Someone acted on it, or what it waited for was settled.
- What to do
- Reload the queue.
- Who can do it
- Any member of the workspace · Open the screen
not_allowed
- What it means
- You may not act on this item of the queue.
- Most frequent cause
- An item that waits for another person, or one you asked for yourself (four eyes).
- What to do
- Leave it to the person it waits for, or to an owner or admin.
- Who can do it
- Any member of the workspace · Open the screen
delegate_to_self
- What it means
- An item is not delegated to yourself.
- Most frequent cause
- Your own name chosen in the list.
- What to do
- Choose another member.
- Who can do it
- Any member of the workspace · Open the screen
delegate_not_allowed
- What it means
- The member chosen may not act on this item, so it cannot be delegated to them.
- Most frequent cause
- A member without the role it needs, or the person who asked for it.
- What to do
- Choose an owner, an admin, or the member the item names.
- Who can do it
- Any member of the workspace · Open the screen
worker_secret_invalid
- What it means
- A scheduled job or an internal route of the deployment was called without its secret, so nothing ran.
- Most frequent cause
- A call that did not come from the deployment’s scheduler or its own tooling, or a scheduler set up with another secret than the server’s.
- What to do
- This route is called by the deployment’s scheduler only, with its secret. If you run this deployment, give the scheduler the same secret as the server.
- Who can do it
- Azoth, or the operator of this deployment
already_exists
- What it means
- What the request would add exists already: the name, address or value it gives is taken, so nothing was added.
- Most frequent cause
- The same form sent twice, or a name or value another item of the workspace uses.
- What to do
- Something with this name or value exists already, so nothing was added. Choose another one, or use the one that exists.
- Who can do it
- Any member of the workspace
operation_in_progress
- What it means
- The same operation is already running for this workspace, so this request did nothing.
- Most frequent cause
- A double click, or two people or processes starting it at the same moment.
- What to do
- This is already being done for this workspace. Wait a minute, reload, then try again if it is still needed.
- Who can do it
- Any member of the workspace
method_not_allowed
- What it means
- The route does not take this HTTP method; the answer’s
Allowheader names the one it takes. - Most frequent cause
- A link or a script sending GET to a route that expects POST — signing out, for instance, is never done from a link.
- What to do
- This action is not done from a link. Use its button in the app, or send the method the route takes.
- Who can do it
- The developer of the calling code
integration_not_connected
- What it means
- The integration this action needs — GitHub, Slack, Microsoft Teams, single sign-on or a model endpoint — is not set up for this workspace.
- Most frequent cause
- It was never connected, or it was removed since.
- What to do
- This integration is not set up for this workspace yet. An owner or admin sets it up in Settings, then try again.
- Who can do it
- An owner or admin of the workspace
integration_failed
- What it means
- The service of an integration — GitHub, Slack, Microsoft Teams — refused or failed the request Azoth sent it, so nothing was done. The answer gives its HTTP status (
vendorStatus) and its own error code (vendorCode), never its text. - Most frequent cause
- Its app was uninstalled or lost a permission, the item asked for no longer exists there, or the service is down.
- What to do
- The integration’s service refused the request. Check that its app is still installed with its permissions, then try again later.
- Who can do it
- An owner or admin of the workspace