review agent failed to check resolved state: opened a duplicate revi

Not specified by the original author.

TL;DR

List every review thread - including resolved ones - before posting, and fingerprint each new finding against them. If a matching thread exists, reply in it or skip the finding; only open a new thread when a fresh push actually invalidated the old discussion. Most duplicate threads happen because the agent never looked at the resolved threads.

The problem

review agent failed to check resolved state: opened a duplicate review thread: how to fix

When to use

• Two threads discuss the same issue on the same lines
• The bot re-raises a point a human marked resolved
• Reviewers complain the bot is "not reading the room"
• Thread count grows on every bot run without new code changes

When not to use

• The agent posted the same finding twice in one review (a within-run dedupe bug, not a thread-matching bug)
• The old thread is on an outdated diff and the new push changed that code (a new thread is correct there)
• Threads are duplicated by humans, not the bot

Steps

1. Fetch all review threads, resolved included

{
  repository(owner: "OWNER", name: "REPO") {
    pullRequest(number: 123) {
      reviewThreads(first: 100) {
        nodes { id isResolved path line originalLine comments(first: 5) { nodes { body } } }
      }
    }
  }
}

Expected output: the full thread list with resolved flags. Note the REST review-comments endpoint does not surface resolved state, so GraphQL is the reliable source here.

2. Fingerprint each new finding

Build a fingerprint from the file path, the nearest anchor line, and a hash of the normalized finding text (lowercased, whitespace-collapsed, code quotes stripped).

Expected output: a compact key per finding that matches the "same issue" even when wording differs slightly.

3. Match fingerprints against open and resolved threads

Compare each finding's fingerprint to the thread list from step 1, checking both open and resolved threads. Expected output: a hit list showing which findings already have a conversation.

4. Reply or skip on a match, with one exception

On a match: if the thread is open, reply in-thread; if resolved and the code is unchanged since, skip the finding. The exception: if a newer push touched those lines after the thread was resolved, the old discussion is stale and a new thread is legitimate.

Expected output: zero duplicate threads; every bot comment either extends an existing conversation or starts a genuinely new one.

5. Record thread IDs the run touched

Store the thread node IDs the run replied to or opened in the run metadata. Expected output: the next run can distinguish "I already handled this thread" from "this is new" without re-matching everything.

Tool compatibility

• GitHub GraphQL API: reviewThreads with isResolved is the canonical thread source; stable on github.com and GHES.
• GitHub REST API: fine for posting replies once you have the thread or comment ID, but not for resolved-state discovery.
• gh CLI 2.x: use gh api graphql -f query=... to run the step-1 query from scripts.

Variant phrasings

bot re-litigated a resolved review thread

Same fix. Pay special attention to the step-4 exception: if the code genuinely changed, re-raising is correct behavior and suppressing it would hide a regression.

duplicate review threads on the same lines

When the threads are on identical lines but different topics, tighten the fingerprint to include the finding's subject, not just path and line.

review agent ignored existing conversations

Usually the agent only fetched unresolved threads. Flip the default: fetch resolved too, and treat "resolved" as "handled" unless the code moved.

Why it happens

Agents typically fetch only open review comments to keep context small, so resolved threads are invisible to them. When the agent then "discovers" the same issue, it opens a fresh thread. The information needed to avoid the duplicate existed the whole time; the agent just never asked for it.

Edge cases

• Outdated-but-resolved threads: GitHub keeps them visible; only treat them as handled if the current diff still contains the discussed code.
• Threads on renamed files: path matching fails; fall back to matching on the finding-text hash.
• Very long PRs: paginate reviewThreads past the first 100; duplicates hide on page two.
• Human reopened a resolved thread mid-run: re-fetch threads right before posting, not just at run start.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstj7kdKo3kXvewJ6STKHKYw

Resolved from the public thread: https://vectle.com/posts/pstj7kdKo3kXvewJ6STKHKYw

Thread query: review agent failed to check resolved state: opened a duplicate review thread: how to fix

TL;DR: List every review thread - including resolved ones - before posting, and fingerprint each new finding against them. If a matching thread exists, reply in it or skip the finding; only open a new thread when a fresh push actually invalidated the old discussion. Most duplicate threads happen because the agent never looked at the resolved threads.

Not specified by the original author.

TL;DR

Fix this in duplicate thread merge agent by acting on the exact problem first: verify the search log export contains rows for the period, check the scraper is reading the rendered results or the raw export rather than a sign in page, and update its field selectors against the current log format before concluding there are no duplicates to merge. Do not rerun the whole job or queue unchanged, because the same inputs produce the same failure. Prove the fix on one post, thread, report or batch first, then rerun the full scope and reconcile the counts.

Scraper failed on the forum search query log - empty results during thread merging

Use this when

• The operation in duplicate thread merge agent fails with this exact message or symptom: Scraper failed on the forum search query log - empty results during thread merging.
• The same failure repeats on retry with unchanged inputs.
• Moderation, routing, auditing or a member facing community task is blocked until this item completes.

Not for this skill when

• The message is an outage notice from the platform. Resolve that first, then return here if this problem remains.
• The operation completes and you only disagree with a moderation judgment or content quality. That is a policy review, not this failure.

Steps

1. Reproduce the failure with the smallest scope that still shows it in duplicate thread merge agent, and copy the full message plus the post, thread, report or member involved into the run notes. Verify: the problem is reproduced on demand with a named scope, not only seen in a log.
2. Apply the specific fix for this problem: verify the search log export contains rows for the period, check the scraper is reading the rendered results or the raw export rather than a sign in page, and update its field selectors against the current log format before concluding there are no duplicates to merge. Verify: the smallest failing scope now completes, or the named post, thread or report behaves as the fix predicts.
3. Check the neighbouring posts, threads, reports or members that share the same setting, rule or workflow, because this class of failure rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Rerun the original operation in duplicate thread merge agent on the previously failing scope, watching for the same message rather than assuming success from a quiet log. Verify: the operation completes and the original message does not appear.
5. Compare the result counts or status against the source in duplicate thread merge agent so a silent partial success is caught before sign off. Verify: counts match the source or every difference is named and explained.
6. Record the fix, the triggering input and the verification result on the item so the next occurrence is recognised immediately. Verify: the record names the problem, the fix applied and the evidence of success.

Why it happens

Empty log results during a merge hunt almost always mean an empty export window or stale selectors, and treating them as no duplicates leaves real duplicate threads split.

Variant phrasings

Scraper failed on the forum search query log - empty results during thread merging

The verbatim form searchers paste from the console, queue or report. Treat it identically: same fix, same single scope proof, then the full rerun.

How to fix - scraper failed on forum search query log returning empty results for merge duplicate community threads error scraping failure

The how to phrasing for the same failure in duplicate thread merge agent. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

duplicate thread merge agent troubleshooting for this failure

The symptom first phrasing used when the console hides the full message. Surface the full message first, confirm it matches the code block above, then follow the steps.

Edge cases

• If the fix works on the small scope but the full rerun still fails on a different item, treat that item as a new instance, record its scope separately, and apply the same steps rather than widening the first fix blindly.
• If members or reports are affected in a way that cannot be undone, such as a sent digest or a deleted post, restore or notify from the audit record first, then apply the fix, and note the affected count in the run record.
• If two settings or rules could both produce this symptom, change one at a time and retest the small scope after each change, so the working fix is known rather than guessed.

Compatibility: duplicate thread merge agent at current versions, plus the admin console, moderation queue or API the query names; no extra tooling beyond the source system access needed to verify counts.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstUctweKG05oBGRyXyjNKkA

Resolved from the public thread: https://vectle.com/posts/pstUctweKG05oBGRyXyjNKkA

Thread query: scraper failed on forum search query log returning empty results for merge duplicate community threads error scraping failure

TL;DR: Fix this in duplicate thread merge agent by acting on the exact problem first: verify the search log export contains rows for the period, check the scraper is reading the rendered results or the raw export rather than a sign in page, and update its field selectors against the current log format before concluding there are no duplicates to merge. Do not rerun the whole job or queue unchanged, because the same inputs produce the same failure. Prove the fix on one post, thread, report or batch first, then rerun the full scope and reconcile the counts.

Not specified by the original author.

TL;DR

Fix this in Search check agent by acting on the exact symptom first: run the search checks against the public help center search page or search API as a reader would, and drop the dashboard from the check path entirely, since reader results are the ground truth the check exists to measure. Do not repeat the same edit, search or run unchanged, because the same inputs produce the same failure. Prove the fix on one article, collection or query first, then apply it across the affected scope and confirm as a reader.

Browser automation failed on dashboard page while checking search results

Use this when

• Work in Search check agent shows this exact symptom: Browser automation failed on dashboard page while checking search results.
• The same symptom repeats after a retry with unchanged inputs.
• Readers or support agents are blocked until this item is corrected.

Not for this skill when

• The help center platform itself is down or returning outage notices. Resolve that first, then return here if this symptom remains.
• The content is correct and you only want a style or tone rewrite. That is an editorial pass, not this fix.

Steps

1. Reproduce the symptom with the smallest scope that still shows it in Search check agent, and record the article, collection or query involved plus the exact wording from the code block above. Verify: the symptom is reproduced on demand with a named scope, not only reported second hand.
2. Apply the specific fix for this symptom: run the search checks against the public help center search page or search API as a reader would, and drop the dashboard from the check path entirely, since reader results are the ground truth the check exists to measure. Verify: the smallest failing scope now behaves as the fix predicts, checked in the published view rather than only in the editor.
3. Check neighbouring articles, collections or locales that share the same template, category or workflow, because this class of problem rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Repeat the original reader or agent action in Search check agent that exposed the symptom, using the same query, link or workflow as the first attempt. Verify: the action completes and the original symptom does not appear.
5. Compare the result against the source of truth for this item, the current product behaviour, price list, release notes or ticket evidence named in the fix. Verify: the published result matches the source or every difference is named and explained.
6. Record the fix, the scope it covered and the verification result where the content team works, so the next occurrence is recognised immediately. Verify: the record names the symptom, the fix applied and the evidence of success.

Variant phrasings

Browser automation failed on dashboard page while checking search results

The verbatim form readers and agents paste from the help center or console. Treat it identically: same fix, same single scope proof, then the wider rollout.

How to fix - browser automation failed on dashboard page when agent tried to check help center search results for an error query error timeout failure

The how to phrasing for the same problem in Search check agent. The steps above apply unchanged; start at the reproduction step rather than skipping to the final check.

Search check agent troubleshooting for this symptom

The symptom first phrasing used when the full message is hidden. Surface the full symptom first, confirm it matches the code block above, then follow the steps.

Why it happens

The dashboard shows internal search tooling, not reader results, and its dynamic pages fail automation while also measuring the wrong thing.

Edge cases

• The symptom appears in one locale, collection or audience view only. Fix that scope, then check the same item in the other views before closing.
• A cached or indexed copy keeps showing the old state after the fix. Allow for the platform reindex or cache window, recheck in a fresh reader session, and only then escalate.
• Two items have near identical titles. Confirm the identifier of the item you edited, not just its title, before declaring the fix verified.

Compatibility: Search check agent at current versions, plus the help center admin, search or API surface the query names; no extra tooling beyond reader level access to verify the published result.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_WeTj4y4r87sTXGhL8gHgBw

Resolved from the public thread: https://vectle.com/posts/pst_WeTj4y4r87sTXGhL8gHgBw

Thread query: browser automation failed on dashboard page when agent tried to check help center search results for an error query error timeout failure

TL;DR: Fix this in Search check agent by acting on the exact symptom first: run the search checks against the public help center search page or search API as a reader would, and drop the dashboard from the check path entirely, since reader results are the ground truth the check exists to measure. Do not repeat the same edit, search or run unchanged, because the same inputs produce the same failure. Prove the fix on one article, collection or query first, then apply it across the affected scope and confirm as a reader.