> For the complete documentation index, see [llms.txt](https://ailyze.gitbook.io/ailyze-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ailyze.gitbook.io/ailyze-docs/troubleshooting/analysis-issues.md).

# Analysis Issues

This page helps you fix problems that come up when you run an analysis or read the results.

## "My project is stuck on Processing"

Analysis runs in the background and takes time, because a deep, structured analysis is slower than a quick chat answer.

1. Open the project to watch **partial results** appear as they stream in.
2. Expect larger datasets and more [themes](/ailyze-docs/reference/glossary.md#theme) or questions to take longer.
3. If the status shows **Error** or **Failed**, use **Restart** from the list, or re-create the project with fewer files or items.

You also get an **email** when the analysis is done, so you don't have to keep the page open.

## "I can only get 1 theme / 1 question"

The **Free Plan** limits each analysis to 1 theme and 1 question.

1. Upgrade to unlock unlimited themes and questions.

For what each plan includes, see [Plans, Limits & Credits](/ailyze-docs/reference/plans-limits-and-credits.md).

## "Action buttons are disabled"

A button is greyed out either because it is a Pro feature or because the analysis is still running.

1. If you see **"Only allowed for paid users"**, know that Download, Share, Add File, Add Theme, Add Question, Edit Codebook, and Accuracy are **Pro** features — upgrade to use them.
2. If a button is disabled **while analysis is in progress**, wait for the analysis to finish.

## "I was asked to pay or pick a sample"

A large spreadsheet analysis goes over the free word allowance, so you are asked to choose how much to analyze before any charge.

1. Pick a **random sample** to keep the cost down.
2. Or choose the **full data** and confirm the charge shown on screen.

The exact rate appears before you submit — see [Plans, Limits & Credits](/ailyze-docs/reference/plans-limits-and-credits.md).

## "The themes aren't quite right"

The AI makes a first pass on its own, so it may miss the angle you care about until you steer it.

1. Regenerate with an instruction, such as *"3 themes focused on X, Y, Z."*
2. Rename, merge, or split themes in the [codebook](/ailyze-docs/reference/glossary.md#codebook) editor (Pro).
3. Add context in the research-context step for documents, or the report instructions for spreadsheets.
4. Or supply your own themes so the AI codes to them.

## "My spreadsheet results look wrong"

Most of the time a column was tagged as the wrong type, so the analysis read it the wrong way.

1. Re-check how each column is tagged: ratings as numerical, single choices as categorical, open-ended text as text, grouping columns as [segments](/ailyze-docs/reference/glossary.md#segment), and junk columns as not analyzed.

For help with segments, see [Compare groups & segments](/ailyze-docs/analyze-data/compare-groups-segments.md).

## "I expected one project but got several"

Choosing **"Analyze across all columns"** creates one overall project plus one project per open-ended column, by design.

1. Read the success message — it lists exactly what you'll get.
2. Choose **selected columns** instead if you want a single focused project.

## "Quotes or counts look off"

AI output always needs a human check, so a stray quote or count can slip through.

1. Verify quotes against the source text.
2. Audit the checklist and justifications tab.
3. Run **Calculate AI Accuracy** (Pro) for a scored check.
4. Use **Add Theme** or **Add Question** for new analysis — the in-app chatbot is for summaries, not deep re-analysis.

## Still stuck?

Re-create the project with a smaller scope to isolate the problem, then contact support with what you saw.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://ailyze.gitbook.io/ailyze-docs/troubleshooting/analysis-issues.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.