List performance findings sixty has surfaced for this org: regressions introduced by a release, and standing problems that were wrong from the start. Ranked by severity. Start here when asked to find or fix performance problems, N+1 queries, slow endpoints, or regressions. Returns ids to pass to get_finding.

Everything needed to fix one finding: the exact measurement, every captured stack frame, the normalized SQL, which child operations account for the change, other findings sharing the same root cause, and what usually causes this kind of problem. Read this before changing any code — the file in the list view is often the symptom rather than the cause.

Take a finding so no other agent starts on the same one. Call this after get_finding and before writing any code. If it answers that somebody else holds it, do not work on it — pick the next finding from the list instead. The claim lasts 30 minutes and is released automatically when you close the finding, or when it expires if you stop. Claim it again to extend it if the work runs long; claiming something you already hold is safe and just renews the lease. Use release:true only if you are abandoning the work without a fix.

Record what happened to a finding, and describe the solution. Use resolved only once a release carrying the fix has reported and the numbers have moved — writing the code is not evidence that it worked. Use dismissed only for something that is genuinely not a problem. Both require a note, because the status says a finding left the list and the note is the only record of why: the diff that fixed an N+1 is not findable six weeks later from a timestamp. Use open to undo either. If unsure, leave it open and say so — an open finding costs someone a glance, a wrongly closed one costs an incident.

Whether telemetry is actually arriving, and if not, why not — never reported, reported and stopped, or arriving with no release attached (which produces an empty feed forever, and looks exactly like a healthy app). Use after installing, and any time the feed is empty and that seems surprising.

Fetch the current install instructions from the collector, for the kind of project this is. Call with no kind to see the options. The instructions are written to be followed against a repository you can read: they name outcomes rather than file paths, because where the code goes depends on the framework and putting it in the wrong place fails silently.