---
description: Rate AI Analyst answers, report a problem with an answer, report a bug from Studio, and learn where feedback and reports go.
---

# Rating answers and reporting problems

You can give feedback in two ways:

- **Rate an answer** with a thumbs up or thumbs down, and an optional comment. Your data team sees these ratings in Studio.
- **Report a problem** when something went wrong, in your own words. Reports go to the support route described in [Where reports go](#where-reports-go).

## Rate an answer

!!! info "Availability"
    - **Who can do this:** members with the **Chat** capability in the active Workspace, in conversations they can reply to.

Under each completed answer, you see two thumbs buttons: **Good response** and **Bad response**.

1. Click **Good response** (thumbs up) or **Bad response** (thumbs down). A comment box opens.
2. Optionally, type a comment in **Add a comment (optional)…**. Comments can be up to 2,000 characters.
3. Press **Enter**, or click the check mark (**Send**), to save your rating.

    To discard it instead, press **Escape** or click **Cancel** (the X).

Nothing is saved until you send it. After you send it, the answer shows **Positive feedback** or **Negative feedback**, followed by your comment.

<!-- screenshot: explorer-answer-feedback -->

Keep in mind:

- A rating applies to one answer, not to the whole conversation.
- You can't change or remove a rating after you send it.
- Ratings don't change how the analyst behaves. They help your data team see where the analyst works well and where it needs improvement.
- If your comment is too long or the rating can't be saved, you see **Couldn't save your feedback.** Shorten the comment and try again.

### When you don't see the thumbs

The rating buttons and **Report a problem** only appear on finished answers, in conversations you can reply to. You don't see them when:

- The conversation was shared with you in read-only mode.
- The analyst is no longer available to you.
- The conversation was migrated from the previous product.
- The answer failed or is still running.

### How your data team uses ratings

Members with the **Edit** capability can review an analyst's conversations in Studio, including the ratings and comments people left:

1. In Studio, go to **AI Analysts** and open the analyst.
2. Click **Monitoring**.
3. In the **Tasks** view, open **Filters**, and under **Feedback** choose **Thumbs up** or **Thumbs down**.

The conversation replay shows each saved rating and comment. See [Traces](../../ai-analysts/monitoring/traces.md).

## Report a problem with an answer

!!! info "Availability"
    - **Who can do this:** members with the **Chat** capability in the active Workspace, in conversations they can reply to.
    - **Deployment:** problem reporting must be turned on for your deployment. See [Where reports go](#where-reports-go).

Use **Report a problem** when an answer is wrong, incomplete or broken in a way you want someone to look into.

1. Under the answer, click **Report a problem**.
2. In **What went wrong?**, describe what happened: what you asked, what you expected and what you got. You can write up to 5,000 characters.
3. Click **Send report**.

When the report is sent, the dialog shows **Thanks for the report.** Click **Close**.

<!-- screenshot: explorer-report-a-problem -->

### What is sent with your report

Along with your description, the report includes:

- The address of the page you were on.
- References to the conversation and the answer you reported, so the problem can be traced. These references are only kept if they belong to your organization and Workspace.

On Actian SaaS and on self-managed deployments that send reports to Actian, the report also includes your email address, so support can follow up. Reports kept on an air-gapped installation don't include it.

Each report is also recorded in your organization's [audit log](../../governance/audit-logs.md).

### If the report doesn't send

| Message | What it means | What to do |
| ------- | ------------- | ---------- |
| **You've sent several reports just now. Please wait a moment before sending another.** | You sent several reports in a short time. | Wait several minutes, then try again. |
| **Problem reporting isn't available right now.** | Your deployment isn't set up to receive reports. | Contact your administrator. |
| **Couldn't send your report. Please try again.** | The report couldn't be delivered. | Try again. If it keeps failing, contact your administrator; problem reporting may be turned off on your deployment. |

If you send exactly the same report twice within a couple of minutes, the second one is treated as already sent.

## Report a bug from Studio

In Studio, you can report a bug that isn't tied to a particular answer:

1. In the left navigation, under **Resources**, click **Report a Bug**.
2. In the **Report a bug** dialog, describe what you did, what you expected and what happened.
3. Click **Submit report**.

The report includes your description and the address of the page you were on. On Actian SaaS and on self-managed deployments that send reports to Actian, it also includes your email address. Reports kept on an air-gapped installation don't.

**Report a Bug** only appears when your deployment accepts reports.

The Steward chat in Studio also has its own **Report a problem** option, which attaches the current Steward session to your report.

## Where reports go

Where your report ends up depends on how your deployment is set up.

| Deployment | What happens to a report |
| ---------- | ------------------------ |
| Actian SaaS, or a self-managed deployment that isn't air-gapped, with support reporting set up | The report goes to the Actian support team. It may also open a support ticket in your name. |
| Air-gapped self-managed deployment | The report stays on your installation. An administrator with the **Manage organization** capability can include it in the diagnostic export they send to Actian. The Studio dialog reads: "Your report stays on this installation; an administrator includes it in the diagnostic export for Actian." |
| Reporting not set up | **Report a Bug** isn't shown in Studio, and **Report a problem** under an answer shows an error when you send. |

If you're not sure how your deployment is set up, ask your administrator.

## Problems the Analyst flags on its own

You don't have to report everything yourself. While it works, the Analyst can flag two kinds of problems. Both show up as steps under the answer:

- **Send semantic-layer feedback**: a gap in your semantic layer that your data team could fix, such as a missing Metric or an unmodelled field. Failed queries caused by the semantic layer or the warehouse are also reported to your data team automatically. These reports go to the Steward's **Inbox** in Studio, not to Actian.
- **Note an issue**: a problem with AI Analyst itself. The Analyst records a short diagnostic note for Actian engineering. Depending on how your deployment is set up, the note is sent to Actian or kept on your installation.

See [How answers are built](how-answers-are-built.md#when-the-analyst-flags-something-for-your-data-team) for what each one sends and what happens next.

## Related pages

- [How answers are built](how-answers-are-built.md)
- [Asking Questions](asking-questions.md)
- [Accuracy and Limitations](../../governance/accuracy-and-limitations.md)
- [Steward Inbox](../../steward-ai-agent/steward-inbox.md)