> ## Documentation Index
> Fetch the complete documentation index at: https://docs.altrum.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Error messages

> Look up a message Altrum showed you, find out what it means and what to do.

Every message in Altrum says what failed and what to do. This page lists the ones you are most likely to see in the product, word for word, so you can search for them. Errors your application gets from the AI Gateway are in the API reference: [Errors](/api-reference/errors.md). Quote the request reference when you contact support.

## Signing in and access

| Message | What to do |
| - | - |
| The email or password is incorrect. Check them and try again, or reset your password. | Check both, or [reset your password](/sign-in.md#set-or-reset-your-password). |
| You are not signed in, or your session has ended. Sign in again. | Sign in again. Sessions end after 8 hours idle or 7 days. |
| This link is invalid or has expired. Ask for a new one. | Invitation links last 7 days and reset links one hour, and each works once. Ask for a new one. |
| Your account is disabled. Ask an owner or admin of your organization to enable it. | Ask an owner or admin. |
| Your organization is inactive. Contact Altrum support to restore access. | Contact Altrum support. |
| Your role cannot do this. Ask an owner or admin of your organization. | See [Members and roles](/members-and-roles.md). |
| Sign in with Google is not available right now. Use your email and password, or try again later. | Use your password, or try later. |
| Too many attempts. Wait N minutes and try again. | Wait for the time shown. |

## Members

| Message | What to do |
| - | - |
| Only an owner can change an owner or make someone an owner. Ask an owner of your organization. | Ask an owner. |
| You cannot change the role of yourself. Ask another owner or admin of your organization. | The same message says "disable yourself" or "remove yourself" for those actions. Ask someone else. |
| An organization must keep at least one active owner. Make another member an owner first, then try again. | Make someone else an owner first. |
| That address already has an Altrum account. Ask them to sign in, or invite a different address. | One address belongs to one organization. |
| That address already has an open invitation. Resend it from the invitations list instead. | Use **Resend** under the members table. |

## AI systems

| Message | What to do |
| - | - |
| Your organization already has an AI system with that name. Choose a different name. | Names are unique, ignoring capital letters. |
| Your organization already has a project with that name. Choose a different name. | Project names are unique, ignoring capital letters. |
| That project does not exist. | It was deleted, or the link belongs to another organization. Open **Projects** to see yours. |
| Choose an active member of your organization. | A project's lead and members are active members. Invite the person first, or wait for them to accept. |
| Only owners and admins can change this. The project's lead can change its description and members. | Ask an owner or admin, or the project's lead for its description and members. |
| The owner must be an active member of your organization. | Choose an active member as owner. |
| You can register an AI system that you own. Ask an owner, an admin or a Governance Lead to name someone else. | A Member registers AI systems with themselves as owner. Leave the owner as you, or ask one of them. See [Members and roles](/members-and-roles.md). |
| This AI system is still being set up. Try again in a few minutes. | Altrum is finishing a new AI system. Nothing is lost. |
| Say why the level is lower than suggested, in at least 10 characters. | A level below the one the rules give needs a reason. See [Risk rating](/ai-systems/risk-rating.md#choosing-a-different-level). |
| A prohibited practice cannot be given another level. | The rating of a prohibited practice is always Very high. Change the answer if it was wrong. |
| Only owners, admins, Governance Leads and the AI system's own owner can change its risk profile. | Ask one of them. This also applies to accepting or rejecting a suggestion from an assessment. |
| That suggestion was already decided or replaced by a newer assessment. Reload the page to see where it stands. | Someone accepted or rejected it first, or a newer assessment replaced it. Reload. |
| Say why, in at least 10 characters. | Rejecting a suggestion, sending an AI system back or pausing it needs a reason. |
| Your organization could not be found. Sign in again. | Your session no longer matches an organization. Sign out and sign in again. |

## Discover

| Message | What to do |
| - | - |
| That key has sent no traffic outside an AI system. | The key belongs to an AI system, to another organization, or has sent nothing. Open **Discover** to see the traffic you can dismiss. |
| That traffic is not dismissed. | It was brought back already. Open **Discover**, **Dismissed**. |
| Say why this traffic needs no AI system. | Dismissing asks for a reason, up to 500 characters. |

## Model catalog

| Message | What to do |
| - | - |
| The AI Gateway could not be updated, so nothing changed. Try again shortly. | Approved models only is on and the AI Gateway could not take the change, so the decision or the switch was not saved. Try again. |
| Choose at least one model. | Tick at least one model before you decide. |

## MCP servers

| Message | What to do |
| - | - |
| That MCP server is blocked. Approve it or mark it for review in AI assets to turn it back on. | It was blocked under **AI assets**, **MCP servers**. Change its status there. See [Block a server](/mcp-servers.md#block-a-server). |
| The AI Gateway could not be updated, so nothing changed. Try again shortly. | Blocking or unblocking needs the AI Gateway, which could not take the change, so the status was not saved. Try again. |
| Only an owner or a Governance Lead can change an MCP server's status. | Ask an owner or a Governance Lead. |
| Only an owner, an admin or a Governance Lead can change an MCP server's governance. | Ask one of them. |
| That owner is not a member of your organization. Choose one of your members. | Choose the owner from the list of your members. |
| That MCP server has no tool by that name. Reconnect it to refresh its tools. | The server's tools changed since the page loaded. Reconnect it under **AI Gateway**, **MCP servers**, then try again. |

## Access reviews

| Message | What to do |
| - | - |
| That access review does not exist. | It belongs to another organization, or the link is wrong. Open **Access reviews** to see yours. |
| Choose a due date from today on. | Pick today or a later day. |
| Decide every key first: keep it or revoke it. | Some keys have no decision yet. Choose a flag of **Every key** to find them. |
| This review is complete, so its decisions cannot change. | A completed review is kept as it was. Start a new review. |
| This review is complete already. | Nothing to do. |

## Compliance reports

| Message | What to do |
| - | - |
| The start must be before the end, and at most 400 days apart. | Choose a shorter period. |

## Incidents

| Message | What to do |
| - | - |
| That incident does not exist. | It belongs to another organization, or the link is wrong. Open **Incidents** to see yours. |
| Only owners, admins and Governance Leads can open an incident about this. An AI system's owner can open one about it. | Ask one of them, or the AI system's owner. See [Incidents](/incidents.md#who-can-do-what). |
| Only owners, admins and Governance Leads, the owner of its AI system and the person it is assigned to can change this incident. | Ask one of them, or ask to have it assigned to you. |
| This incident is resolved. Reopen it to change it. | Select **Reopen** and say why, then make the change. |
| Say why the incident is open again. | Reopening asks for a reason. |
| Mark the incident serious before marking it reported. | Switch on **Serious incident** first. |
| That alert does not exist. | The alert belongs to another organization. Open the incident from your own **Alerts**. |
| That request is not in your request log. | The request belongs to another organization, or is older than the log keeps. |

## Assessments

| Message | What to do |
| - | - |
| Only an owner, an admin, a Governance Lead or the AI system's owner can work on its assessment. | Ask one of them. |
| (Name) is working on this assessment. Try again when they are done, or after a few minutes if they have left. | Wait, or ask them. |
| This assessment can no longer be edited. | It was completed or closed. Start a new assessment. |
| This assessment has already been submitted. | Review its results instead. |
| The assistant is still answering the last message. Wait for it to finish, then send yours. | Wait for the reply. |
| The assistant is busy or cannot be reached. Your answers so far are saved: try again in a few minutes. | Try again later. |
| Your documents are still being read. Wait a minute, then send again. | Wait, then send. |
| Altrum has not identified any risks yet. Try again in a few minutes. | Choose **Try submitting again** later. |

## Guardrails

| Message | What to do |
| - | - |
| Only an owner, an admin, a Governance Lead or the AI system's owner can change its guardrails. | Ask one of them. |
| Only an owner, an admin or a Governance Lead can change the organization's guardrails. | Ask one of them. See [Organization guardrails](/guardrails/organization.md). |
| Turn on at least one guardrail before applying. | Switch a guardrail on. |
| Save your guardrail settings first, then apply them. | Choose **Save draft**, then **Apply**. |
| Choose at least one of topics, or switch this guardrail off. | The guardrail named needs a list. The word changes with the guardrail. |
| The guardrail service is busy or cannot be reached. Your settings are saved: try again in a few minutes. | Your draft is kept and the previous version stays live. Try again. |
| The assessment is not complete yet. | Followed by the reason. Fix it, then **Complete Assessment** again. |

## Red-team runs

| Message | What to do |
| - | - |
| Apply guardrails first: a red-team run checks the live version. | [Apply](/guardrails/versions.md) your guardrails, then run. |
| The live guardrails enforce nothing, so there is nothing to check. Turn a guardrail on and apply it. | Every guardrail is off in the live version. |
| A red-team run is already going for these guardrails. Wait for it to finish. | Open the run that is going; it finishes in about a minute. |
| That red-team run does not exist. | It belongs to other guardrails or another organization, or the link is wrong. |

## AI Gateway

Errors your application receives from the AI Gateway, with their codes and what to do, are in the API reference: [Errors](/api-reference/errors.md).

## Something else

If a message is not here, it still says what to do. If it asks you to contact support, raise a ticket with the request reference: see [Support](/support.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.