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

# Troubleshooting Ankra AI

> Find out why Ankra AI did not answer, refused a question or a change, stopped a run, or stays silent in Slack, Teams or a pull request, and put it right.

When Ankra AI does not do what you asked, the portal almost always says why, in one sentence, where you asked. This page lists those sentences by symptom, with what causes each and what to do. Start with the symptom you see.

## Before you start

* Note where you asked: **Ask Ankra** in the portal, the CLI, Slack or Teams, or a pull request. The checks differ.
* Some fixes need a role that manages Ankra AI, such as owner or admin: resuming a stopped Ankra AI, adding a model key, changing a connection. Where a fix needs one, the portal says who can make it.
* The CLI checks below need the Ankra CLI, logged in to your organisation:

```bash theme={null}
ankra ai status
ankra ai autonomy status
```

`ankra ai status` shows the active AI provider and the configured credentials; `ankra ai autonomy status` shows whether autonomous actions are paused or all AI is stopped.

## Ask Ankra is missing, or there is no Mode switch

| What you see | Why | What to do |
| - | - | - |
| `⌘J` does nothing, and **Find** offers no **Ask Ankra** | Your role cannot use Ankra AI | Ask an organisation admin for a role that may use Ankra AI |
| A page reads **Your role cannot use Ankra AI** | The same | As above |
| The composer has no **Mode** switch, and every conversation stays in **Ask** | Your role may use Ankra AI but not act | Ask for a role that may act, or ask someone who has one to make the change |
| The **Ankra AI** row is missing from the sidebar | Your role cannot read agent runs, alerts or the organisation | Ask an organisation admin |
| **Work** is missing from the Ankra AI menu, and the Overview reads **Tickets are not turned on** | Tickets are switched off for your organisation | [Contact support](https://docs.ankra.ai/platform/support.md) |

See [AI Assistant](https://docs.ankra.ai/platform/ai-assistant.md) for who sees what.

## The question was refused

A question that does not reach Ankra AI is answered in the panel with one of these sentences. A person who can fix it also gets a button to the page that does.

| Message | Why | What to do |
| - | - | - |
| **Your role cannot use Ankra AI.** | Your role does not include Ankra AI | Ask an organisation admin |
| **An admin has paused Ankra AI for this organisation.** (or, for someone who manages Ankra AI, **Ankra AI is paused for this organisation.**) | Someone stopped all AI for the organisation | Someone who manages Ankra AI opens **Ankra AI → Autonomy and approvals** and presses **Resume all AI** under **Stop Ankra AI**. The button in the message, **Turn Ankra AI back on**, goes there. See [Stopping Ankra AI](https://docs.ankra.ai/platform/ai-overview.md#stopping-ankra-ai) |
| **Your organisation has used its AI allowance for this month. An organisation admin can add a model key so Ankra keeps answering.** | The monthly allowance for Ankra's default models is used up | An admin presses **Add a model key**, which opens **Ankra AI → Models and provider**, and adds your own provider key. See [Models and cost](https://docs.ankra.ai/platform/ai-provider.md) |
| **Ankra AI is unavailable until the overdue invoice is settled.** | An invoice is overdue | Settle it under **Settings → Plan and billing**; the message's **Open billing** goes there. In the CLI, a one-shot `ankra chat -o json` prints `"error_code": "BILLING_RESTRICTED"` |
| **That was a lot of questions at once. Try again in a minute.** | Too many questions in a short time | Wait a minute and ask again |
| **Ankra is still answering. Wait for the answer, or stop it and ask again.** | A question is already running in this conversation | Wait, or stop it and ask again |
| **A question can contain up to 8,000 characters. Shorten it, or attach the long part as a file.** | The question is too long | Shorten it, or attach the long part. See [Attach a screenshot or a file](https://docs.ankra.ai/platform/ai-assistant.md#attach-a-screenshot-or-a-file) |
| **The organisation changed in another tab. Reload the page to ask here.** | You switched organisation in another tab | Reload the page |
| **Ankra did not confirm it got the question. It may still answer; if nothing appears, ask again.** | The question may not have arrived | Wait a moment; ask again if nothing appears |

When the allowance is used up and Ankra has turned on its DevOps AI model for your organisation, an answer can carry the notice **Your organisation's monthly AI allowance is used up, so this answer comes from the DevOps AI model by Ankra, which has its own monthly allowance.** The answer is real; it comes from a different model.

## The answer stopped before it finished

| What you see under the answer | Why | What to do |
| - | - | - |
| **The AI model behind Ankra stopped responding, so this answer ends here. Ask again to continue.** | The model did not respond in time | Ask again; the conversation keeps its context |
| **Ankra used all the steps one answer may take before the work was done. Continue lets it go on from here.** | The answer reached its step limit | Press **Continue** |
| **This answer is taking many steps. Answer now asks Ankra to answer with what it has.** | The answer is long | Press **Answer now**, or let it carry on |
| **Ankra stopped before it finished.** | The answer failed | Ask again. If it keeps failing, check [The question was refused](#the-question-was-refused) and whether all AI is stopped |
| **You stopped this answer.** | You stopped it | Ask again when you are ready |

In the CLI, a one-shot `ankra chat` that ends on a pause exits with code 9; add `--wait` to follow the conversation through its pauses. See [`ankra chat`](https://docs.ankra.ai/reference/cli/chat).

## A change was refused or never ran

| What you see | Why | What to do |
| - | - | - |
| Ankra AI explains but never proposes a change | The conversation is in **Ask** mode | Switch the composer's **Mode** to **Agent** or **Plan**. See [Choose a mode](https://docs.ankra.ai/platform/ai-assistant.md#choose-a-mode) |
| **No action was queued in this turn. Ask again and a real proposal shows up as a card.** | Ankra AI described a change without proposing it | Ask again, naming the change you want |
| The confirmation is blocked after you approved | The cluster changed since the change was proposed | Read the change again, then ask Ankra AI to propose it against the current state |
| Ankra AI will not touch `kube-system`, `ankra-system`, `cert-manager` or a similar namespace | Writes into protected namespaces are refused in every mode | Make the change yourself, or through the Stack that owns it |
| Nothing changes during an incident although auto-remediation is on | Someone paused autonomous actions | **Ankra AI → Autonomy and approvals → Stop Ankra AI**: **Resume autonomous actions** |
| Changes you approved wait on someone else | Changes, plans and questions from your conversations wait on **Needs you** | Open **Needs you** (`/next/needs-you`) and **Review** or **Answer** each |

What Ankra AI may change without asking is set in five places; [What it can change without asking](https://docs.ankra.ai/platform/ai-overview.md#what-it-can-change-without-asking) lists them.

## The model is not configured

| What you see | Why | What to do |
| - | - | - |
| Answers stop with the allowance message | No provider key, and the allowance is used up | Add your own key under **Ankra AI → Models and provider** |
| `ankra ai status` shows no provider you expect | The key was removed or never added | Add it again. See [Models and cost](https://docs.ankra.ai/platform/ai-provider.md) |

## Slack, Teams or a pull request gets no answer

1. Open **Ankra AI → Gateway**. Each surface shows **Connected** or **Partly connected**; one without a badge is not set up.
2. Press **Set up the gateway** (or **Review the setup**) and open the step for that surface. **What Ankra found** lists what is connected, and the step's state says what is missing: **Not set up**, **Partly set up**, **Could not check** or **Needs an administrator**. See [Set up the AI Gateway](https://docs.ankra.ai/platform/ai-guided-setup.md).
3. For Slack and Teams, check that you linked your own account under **Your account → Connected accounts**: Ankra AI answers with the access of the person asking.
4. For a pull request, check that **AI review** (for automatic reviews) or **Replies to mentions** (for `@ankraai`) is on for that repository under **Ankra AI → Gateway connections**, and for an application under **Applications → \<your application> → Settings → Who runs it**. With **Replies to mentions** on, a mention of `@ankraai` is never filtered by branch scope, draft state or the review budgets. See [AI code review](https://docs.ankra.ai/platform/ai-code-review.md) and [Application AI Settings](https://docs.ankra.ai/platform/application-ai.md).

[AI Connections](https://docs.ankra.ai/platform/ai-connections.md) has the steps for a Slack or Teams app that does not answer.

## A run stopped, or a ticket is not worked

**Ankra AI → Activity** (`/next/ai/agent-runs`) lists every agent run. Filter it to **Failed** or **Waiting for a person**, and open a run: its header says **The run failed**, **Waiting for a person** or **A plan is ready for review**, and **Run activity** shows each step.

| What you see | Why | What to do |
| - | - | - |
| A run is **Cancelled** | Someone stopped it, or someone pressed **Stop all AI** | Check **Ankra AI → Autonomy and approvals**; start the work again once AI is resumed |
| **Waiting for a person** | A plan or a change needs approval | Open the run's ticket, or **Needs you**, and decide |
| A ticket sits on **Work** and nobody works it | No agent is available to staff tickets | Open **Ankra AI → Settings → Configure work routing**. If the **Ankra agent** tab reads **No eligible agent reported**, press **Ask Ankra to check ticket staffing** |
| Every scheduled agent stopped at once | Someone paused autonomous actions, which pauses every AI agent | **Resume autonomous actions** under **Stop Ankra AI** |

From the CLI, read a run in full or its transcript:

```bash theme={null}
ankra ai tasks runs "<agent name>"
ankra agents run <run-id>
ankra agents transcript <run-id>
```

## Where to look next

* **Needs you** (`/next/needs-you`) - every approval, fix and alert that waits on a person.
* **Ankra AI → Activity** - every agent run and its steps.
* [Audit log](https://docs.ankra.ai/guides/audit-log.md) - what changed in your organisation, and who changed it.
* [Contact support](https://docs.ankra.ai/platform/support.md) - with the time, the place you asked and the message you saw.


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