---
title: "Route Sentry issue alerts to one environment | Proofline Help"
description: "Open the Sentry connection from Settings → Connections when alerts arrive but no investigation starts. The linked environments determine whether Proofline can route an issue alert."
url: https://proofline.sh/help/sentry-investigation-routing/
---

[Help center](/help/)

# Route Sentry issue alerts to one environment

Open the Sentry connection from Settings → Connections when alerts arrive but no investigation starts. The linked environments determine whether Proofline can route an issue alert.

## Link the intended environment and inspect the refused alert

Open the connection, choose an **Environment** under **Environment access**, then choose **Link environment**. Repeat for each environment that may use the connection. Choose **Unlink** beneath an environment to remove its access.

A Sentry alert opens an investigation only through a connection linked to exactly one environment. When an alert arrives while the connection serves no environment or several, Proofline opens nothing. The connection's page shows **Latest refused alert** with the newest refused alert: the cause, when the alert happened, when Proofline refused it and how many environments were linked. While the connection still serves no environment or several, its entry in **Telemetry** also shows **Last alert opened no investigation**, even after a metric alert is refused. Link exactly one environment so later alerts open investigations. The mark then leaves **Telemetry**, and the connection's page keeps the refused alert as a record.

## Related guides

-   [Connect Sentry](/help/connect-sentry/)
-   [Create an environment](/help/create-environment/)
