> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/guides-and-quickstarts/evaluations-and-observability/inspect-project-analytics.md).

# Inspect project analytics

Analytics shows workflow usage and individual executions. Use the summary to check activity, then open a run to inspect its inputs, outputs, and errors.

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSQ1Sgy933krTyK0S4JpP%2Fuploads%2FvnpTf6csXv3tGm82OpwD%2FG077.mp4?alt=media&token=7c691632-03b6-4662-8fc0-12daab62568a>" %}

## Before you start

Have the project, approximate request time and time zone, and a non-sensitive part of the input ready. If you do not have access to its analytics, ask the project owner to inspect the run or grant the appropriate access. Use [Debug a recorded run](/guides-and-quickstarts/evaluations-and-observability/debug-a-recorded-run.md) once you have located the relevant execution.

## Choose a date range

Open the project's Analytics page and review runs, users, errors, and token totals together.

![Project Analytics summary](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/GozcbJnn9Fpcep22SVSm/assets/g077-g077-01-overview.png)

A workflow can complete without model tokens if its execution does not use a model.

Choose a reporting period that includes the activity you need to inspect.

![Analytics reporting dates](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/GeymzRVLPHqVmuzFC65g/assets/g077-g077-02-dates.png)

Check the explicit start and end dates before interpreting totals.

## Find failed runs

Open the run table's Filters and select a failure status.

![Run table failure-status filter](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/1UuQby3oT7iVjZsvXVA0/assets/g077-g077-03-filter.png)

Table filters can narrow the rows without changing the summary cards above them.

Open a failed run and follow Flow progress to the first failing node.

![Failed run and Flow progress](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/DrAxFd5nA9NcWjCIPv3i/assets/g077-g077-04-failure.png)

Read the Errors section to identify the execution problem.

## Search individual runs

Clear filters that no longer apply and search the Input column for relevant text.

![Input-column search](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/SawTPzEWj3ZDMKMnz7eU/assets/g077-g077-05-search.png)

Use the request content and time to identify the correct run.

Open the matching run and inspect Output and Errors.

![Matching run Output and Errors](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/r2nPLHIYfkMoi5XzUamX/assets/g077-g077-06-success.png)

Feedback adds user context but does not by itself establish whether the result is correct.

Clear the input search when you need the full run list again.

![Run list after clearing input search](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/A6xPAV58Pfw66Ibwyust/assets/g077-g077-07-reset.png)

Keep the date range and filters in mind when a known execution appears to be missing.

## Important behavior

Summary metrics and the run table may use different filters. Clear table filters before comparing its rows with a summary total.

If a run is missing, check the date range and active filters.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stackai.com/guides-and-quickstarts/evaluations-and-observability/inspect-project-analytics.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.