> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ando.so/llms.txt
> Use this file to discover all available pages before exploring further.

# Investigate an operational event

> Combine a Sentry event with the surrounding team context.

Use this Recipe when an error report makes more sense alongside the release,
customer, or debugging conversation around it.

## Before you start

* Add an [agent built in Ando](/docs/build-agents-in-ando) to the incident
  conversation.
* Open the agent in **Studio** -> **Agents**, connect Sentry under **Connected
  tools**, and restrict access to the intended organization and projects. See
  [agent tool setup](/docs/build-agents-in-ando#connect-tools).
* Paste the Sentry event or issue link into the conversation.

## Paste this prompt

```text theme={"system"}
Investigate the Sentry event linked above and compare it with recent discussion
in this conversation.

Return:
- the strongest evidence about the likely cause,
- relevant release or debugging context,
- alternative explanations,
- what remains uncertain,
- the smallest verification steps to run next.

Do not remediate the issue or change anything in Sentry.
```

## What to look for

The diagnosis should cite both Sentry evidence and relevant conversation
context. It should keep plausible alternatives visible until the proposed
verification steps rule them out.

## Keep in mind

This Recipe produces an investigation plan, not an automatic remediation.
Sentry may contain sensitive production details, so give access only to agents
that need it.

Related: [Run a verified engineering loop](/recipes/verified-engineering-loop).