# Incident calls: find the code path while people are talking

> Five people searching the same repository is slow. Roles, a search order and the sentences that move an incident call from the search to the fix.

Source: https://hintvo.com/blog/incident-call-find-the-code-path-fast | Last updated: November 20, 2026 | Reviewed: 2026-11-20

In an incident call the slow part is rarely the fix. It is five people searching the same repository at once and nobody saying what they found. Give the search one owner, search from the symptom inward, and report in file and line.

## Give the call three jobs

- **One person leads.** They decide, keep time and say what happens next.
- **One person traces the code.** Screen shared, thinking out loud.
- **One person talks to the outside.** Customers, the status page, the rest of the company.

If you are tracing, you are not also leading. The moment one person does both, the call stops moving.

## Search from the symptom inward

1. The exact error text or status code that users see.
2. The log line that goes with it, and the function that writes that line.
3. The caller of that function and the inputs it was given.
4. What changed recently in that file: the last deploy, the last few commits.
5. The setting or flag that controls the behavior.

## Report in a form others can check

"I think it is the gateway" gives the room nothing to do. "payments/charge.ts throws when the gateway times out, and the consumer does not retry" gives them a line to read and a decision to make. Say what you ruled out as well, so nobody checks it twice.

## Decide: stop the damage, or fix the cause

- Can we turn it off with a flag?
- Can we roll back the last deploy?
- Is data being damaged right now, or only delayed?

If any answer points to a fast way of stopping the damage, take it first. The cause can wait an hour. Customers cannot.

## Before you hang up

- Write the timeline while everyone still remembers it.
- List the action items, each with an owner and the files it touches.
- Note what monitoring would have told you earlier.

> **Where Hintvo fits:** in an incident call, Hintvo shows the function people are asking about with its file and line, and one click opens it in VS Code, Cursor or Zed. When you stop listening, it writes notes with action items and the files they touch. Meeting notes need a pack of hours. See [how it helps developers in meetings](https://hintvo.com/meeting-assistant-for-developers).

## Related

- [AI meeting assistant for developers, with answers from your code](https://hintvo.com/meeting-assistant-for-developers.md): How does Hintvo AI help in sprint planning, design reviews and incident calls?
- [Meeting notes developers actually use](https://hintvo.com/blog/meeting-notes-developers-actually-use.md): What should technical meeting notes contain so that people use them?
- [How to answer questions about code you did not write](https://hintvo.com/blog/answer-questions-about-code-you-did-not-write.md): How do I answer a question in a meeting about code I did not write?
