---
title: "Fix an instrumentation review finding | Grafana Cloud documentation"
description: "Open an instrumentation review finding from GitHub in Grafana Assistant Workspace and prepare a focused code fix."
---

> For a curated documentation index, see [llms.txt](/llms.txt). For the complete documentation index, see [llms-full.txt](/llms-full.txt).

# Fix an instrumentation review finding

Grafana Assistant can turn a published instrumentation review finding into a new Workspace conversation. Start from the finding on GitHub to carry its repository, pull request, code location, and review details into the conversation.

## Before you begin

Your Grafana instance needs instrumentation review and Workspace enabled. Your administrator must connect the GitHub App and select the repository for review and agent access. You also need Assistant chat access and an available coding environment to implement changes.

The pull request must still be open and ready for review. For a pull request from a fork, your administrator must also enable external pull request review for the repository.

## Open the finding in Workspace

Click **Fix in Grafana** beneath the finding on GitHub. Sign in to the linked Grafana instance if prompted. After Assistant verifies the finding and your access, it starts a new Workspace conversation automatically. You don’t need to copy the finding or send another message.

To ensure Workspace opens in a new tab while keeping GitHub open, Ctrl-click (Windows/Linux) or Cmd-click (macOS) the button. GitHub may ignore the button’s new-tab setting.

The initial finding item shows the issue title, repository, pull request, and file location. Use **View original review comment** to return to the GitHub thread, or **View pull request** to inspect the full change. If the original comment is no longer available, the pull request link remains available.

Expand **Finding details** to read the evidence and suggested remediation. Assistant receives the complete finding context even while these details are collapsed. The finding card remains available when you refresh or reopen the conversation; reopening it does not start another fix.

## Review the proposed fix

Assistant is asked to check whether the finding still applies to the current pull request, make a focused change, and run relevant tests. Starting the conversation doesn’t approve publishing code or changing live Grafana resources. Review and approve changes through the normal coding workflow.

The coding environment uses the instance’s configured repository access. The fix conversation belongs to you; it doesn’t expose the private conversation used to produce the automatic review.

## Resolve an unavailable finding

If the finding can’t be opened, check that you’re signed in to the correct Grafana instance and still have Assistant access. The review may have expired under the instance’s retention policy, the GitHub connection or repository enrollment may have changed, or the pull request may have closed.

Open the latest review on GitHub and try its **Fix in Grafana** action. For a connection error, select **Retry**. If Assistant terms haven’t been accepted, use the configuration link and ask your administrator to complete setup before retrying.

If Workspace shows **Fix conversation paused**, your finding is still attached. Check your connection or ask your administrator to accept Assistant terms, then select **Retry terms check**. Retry only verifies acceptance; it does not accept terms for you.