> For the complete documentation index, see [llms.txt](https://evidano.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://evidano.gitbook.io/ailyze-docs/troubleshooting/analysis-issues.md).

# Analysis Issues

Fixes for problems running or reading document and spreadsheet analysis.

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

## "Review and start analysis only shows a message"

In document analysis, nothing starts until the configuration is complete.

1. Read the message at the bottom of the screen, for example "Add the themes before creating the project". The column at fault opens, or the section is highlighted in red.
2. Fix that one thing, for example choose **Generate draft themes and sub-themes now** in the themes section, then click the button again.
3. If "N columns need a description" appears, click **Write them with AI** (**Write it with AI** for one) or fill them in, then **Continue**.

## "My project is stuck on In progress"

Analysis runs in the background, and a deep, structured analysis takes longer than a chat answer.

1. Click the percentage on the project list to see which stage it has reached. Early on, clicking the row does the same.
2. Open the project, or **Open partial results** in those details, to read **Partial Results** as they arrive.
3. Expect more files, [themes](/ailyze-docs/reference/glossary.md#theme), or questions to take longer. You get an email when it is done.
4. If the status turns to **Error** (or **Failed**), click **Retry** next to it. If it fails again, create the project again with fewer files or items.

## "My project says Not started"

The analysis never began, so waiting will not help. Hover over the status to read "This project never started analysing. Delete it and create it again."

1. Delete the project with the bin icon in its **Action** column.
2. Create it again. Your files are still in the library, and **Select from recent** finds them quickly.

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

The Free plan runs the whole analysis but unlocks only the first theme and the first question in the results.

1. Upgrade to unlock every theme and question.

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 because it needs the Pro plan, or because something is still running. Hover over it to see which.

1. "Only allowed for paid users": **Export**, **Share**, **Edit project** › **Add theme**, **Add question** and **Delete files**, and the **Codebook** header's **Edit** and ⋯ › **Calculate AI accuracy** need the Pro plan. **Edit project** › **Add file** works on every plan, up to your plan's file count.
2. "This action is disabled while analysis is in progress": wait for the analysis to finish.
3. "Please wait until the current update finishes.": an added file, theme, or question is still being analyzed.

<figure><img src="https://1178311500-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi4GBXPMUDxszIpUVOARU%2Fuploads%2Fgit-blob-8f657c42638b5f993eb037bdf97881f8a4f8a75c%2Fsettings-document-analysis-39-codebook.png?alt=media" alt="Codebook section with Edit and the ⋯ menu in its header, above the themes and codes"><figcaption><p>The codebook tools sit in the Codebook header, not in the action row: 1 Edit and 2 the ⋯ menu with Calculate AI accuracy.</p></figcaption></figure>

## "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. Before you start the analysis, click **Edit themes and sub-themes** under the themes, then **Regenerate draft themes and sub-themes**, and give an instruction, such as *"three themes focused on X, Y, and Z."* The new themes replace yours; **Undo** brings them back.
2. Add context on the first step, under **Supporting files**: a short brief (**Input manually**), or an attached codebook, which is imported word for word.
3. Or bring your own themes: **Add manually**, then **Type**, **Paste**, **Upload**, or **Use previous**.
4. After the run, rename, merge, or split themes with **Edit** in the **Codebook** header (Pro). For spreadsheets, use the report instructions.

## "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; the pencil next to a quote's "Context from AI:" (**Did AI make a mistake?**) explains how to correct it.
2. In a unit-of-analysis section (for example **Outcomes**), counts are units, not documents.
3. Audit the checklist and justifications tab.
4. Run **Calculate AI Accuracy** from the **Codebook** header (Pro) for a scored check.
5. 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.