> For the complete documentation index, see [llms.txt](https://docs.katara.ai/about/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.katara.ai/about/brains/activity.md).

# Activity and refresh

Use **Activity** to inspect refresh work, committed Wiki history and GitHub export history. These are three independent views, not a single event feed or a record of every document-processing step.

## Before you start

Select the correct organization and Brain. You need current read access to inspect its activity; requesting a refresh additionally requires the action's current capability and a ready Brain. Being an organization administrator does not automatically provide those permissions.

## Request and check a refresh

1. Open the Brain's **Activity** tab.
2. Select **Refresh runs** to review existing work before starting another request.
3. If available, choose **Refresh now**.
4. Check the acceptance result, then inspect the resulting refresh run and its read-only details.
5. After completion, return to [Knowledge](https://docs.katara.ai/about/brains/knowledge.md) and inspect the affected pages and freshness information.

An accepted refresh request is queued work, not proof of completion. A newly requested refresh may process current inputs; it is not a replay of a selected historical run and does not promise reuse of an earlier commit or indexing-only work.

Refreshes also do not turn authored narrative back into generated narrative. If a manually maintained page still contains old prose, review that page directly.

## Choose the right history

| View               | What to inspect                              | What it does not establish                                   |
| ------------------ | -------------------------------------------- | ------------------------------------------------------------ |
| **Refresh runs**   | Refresh requests and their reported outcomes | Every uploaded file is indexed or represented in a Wiki page |
| **Wiki history**   | Committed local Wiki changes                 | The same content has reached GitHub                          |
| **Export history** | Export runs and their reported outcomes      | Original files were exported or local sources are fresh      |

Open a record's details for the information actually returned for that record. Treat missing times, revisions or status metadata as unreported, not as a successful or empty result. Load additional records when the selected view offers more; one visible page is not necessarily complete history.

Activity details are read-only. They are not rollback controls. In particular, inspecting an old commit does not restore it, and deleting a source does not erase that commit.

## Investigate a problem

**Refresh now is unavailable:** check Brain readiness, enabled state and current permission. If the service itself is unavailable, follow the [availability guidance](https://docs.katara.ai/about/reference/availability.md); repeatedly submitting work will not fix missing service configuration.

**Upload accepted but no Wiki change:** first check [Sources](https://docs.katara.ai/about/brains/sources.md). Acceptance, extraction, search indexing and a Wiki refresh are different outcomes. Do not infer per-file indexing success from a Brain-wide run.

**Knowledge is current but GitHub is behind:** inspect **Export history** and [GitHub export settings](https://docs.katara.ai/about/brains/github-export.md). Saving configuration alone does not request an export.

**A run fails or its outcome is uncertain:** inspect its details and the current Brain state before requesting new work. Do not assume a historical record can be retried with identical inputs. Preserve the actual reported error when asking an administrator for help.

**Activity becomes inaccessible:** confirm organization selection and ask the owner to review access. An empty or denied view is not proof that history was deleted.
