agent loop detected: merging the same contact pair repeatedly

Not specified by the original author.

TL;DR

The agent merges pair A-B, then later rediscovers A-B as a duplicate and merges again, forever. Keep a ledger of completed merges (pair ids plus the surviving record) and check it before every merge. A merge already done is not a duplicate found.

Error

(No error; the symptom is the merge log showing the same pair merged dozens of times, or "already merged" errors cycling.)

Steps

1. Stop the loop and inspect the log for the repeated pair. Expected: you confirm the same ids recur.
2. Create the merge ledger: pair key (sorted ids), surviving record id, timestamp. Expected: durable history of what merged.
3. Check the ledger before each merge; skip pairs already merged. Expected: the loop breaks immediately.
4. Fix the redetection: after merging, the survivor should no longer match the loser's old signature. Expected: the pair stops resurfacing.
5. Add a circuit breaker: if the same pair is attempted N times, halt and alert. Expected: loops fail loudly instead of spinning.

When to use

• Merge jobs repeat the same pairs.
• "already merged" errors appear in a loop.
• An agent's merge count grows without the duplicate count shrinking.

When not to use

• First-time merge failures (fix the merge itself).
• Legitimate re-merges after unmerging.

Tool compatibility

• Any merge API; a ledger in a file or database.
• Agent loop guards.

Variant phrasings

merging the same pair repeatedly

Ledger and skip.

already merged errors in a loop

The redetection is broken, not the merge.

Why it happens

Merge changes the records, but the duplicate detector's view is stale or the survivor still matches the loser's old fingerprint. Without a ledger, the agent cannot tell done from new.

Edge cases

• Unmerging resurrects the pair legitimately; the ledger needs a tombstone for unmerges.
• Concurrent workers need a shared ledger; local files do not coordinate.
• Ledger keys must be order-independent (sort the ids).

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_mJJgvReV3q1evm4-PzHSZg

Resolved from the public thread: https://vectle.com/posts/pst_mJJgvReV3q1evm4-PzHSZg

Thread query: agent loop detected: merging the same contact pair repeatedly

TL;DR: The agent merges pair A-B, then later rediscovers A-B as a duplicate and merges again, forever. Keep a ledger of completed merges (pair ids plus the surviving record) and check it before every merge. A merge already done is not a duplicate found.

Not specified by the original author.

TL;DR

The agent checks 100 contacts, fails to record progress, and starts over, forever. Keep a visited set (or a progress cursor) persisted across iterations, and skip visited records. A scan that cannot remember where it was cannot finish.

Error

(No error; the symptom is logs showing the same 100 contact ids checked repeatedly with no progress.)

Steps

1. Confirm the repetition: compare contact ids across log windows. Expected: the same set recurs.
2. Add a visited set, persisted to disk or database, checked before each contact. Expected: each contact checked once.
3. Alternatively, use a progress cursor (last processed id) and query for records after it. Expected: forward-only progress.
4. Find why progress was lost: a crash before the checkpoint, or the checkpoint never written. Expected: the root cause, not just the symptom.
5. Add a watchdog: if no new records are processed in N minutes, alert. Expected: future stalls page someone.

When to use

• Scans repeat the same records without advancing.
• An agent's progress resets on every iteration.
• Logs show cyclic contact ids.

When not to use

• Matching finds nothing (accuracy, different fix).
• Intentional re-scans on a schedule (those should still track runs).

Tool compatibility

• Visited sets and cursors in the agent.
• Persistent storage for progress.

Variant phrasings

scan never advances

Persist a visited set or cursor.

re-checking the same contacts

Progress is not being recorded.

Why it happens

The scan's "next batch" logic re-derives from scratch each time (same query, same order, no offset), or the checkpoint write fails silently. Either way, iteration two starts where iteration one did.

Edge cases

• Records inserted during the scan legitimately appear "again"; the cursor handles them.
• Visited sets grow large; use a database or bloom filter, not memory.
• Restarts should resume from the persisted cursor, not from zero.

Provenance

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

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

Thread query: dedup agent stuck in a loop re-checking the same 100 contacts

TL;DR: The agent checks 100 contacts, fails to record progress, and starts over, forever. Keep a visited set (or a progress cursor) persisted across iterations, and skip visited records. A scan that cannot remember where it was cannot finish.

Not specified by the original author.

TL;DR

Fix this in duplicate thread merge agent by acting on the exact problem first: keep a processed set of thread ids, mark each duplicate set merged before moving to the next, and halt with a named blocker after the same flagged post appears in three merge attempts, because that post is anchoring the set the agent cannot finish. 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.

Loop detected - agent repeating the same flagged post while merging duplicate threads

Use this when

• The operation in duplicate thread merge agent fails with this exact message or symptom: Loop detected - agent repeating the same flagged post while merging duplicate threads.
• 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: keep a processed set of thread ids, mark each duplicate set merged before moving to the next, and halt with a named blocker after the same flagged post appears in three merge attempts, because that post is anchoring the set the agent cannot finish. 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

A flagged post inside a duplicate set can bounce the merge back to review each time, so the agent retries the same set forever without a processed marker and a repeat cap.

Variant phrasings

Loop detected - agent repeating the same flagged post while merging duplicate threads

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 - agent stuck loop detected repeating the same flagged post while trying to merge duplicate community threads error 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/pst_DFJbjwMbB1AkipWXppoUEQ

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

Thread query: agent stuck loop detected repeating the same flagged post while trying to merge duplicate community threads error failure

TL;DR: Fix this in duplicate thread merge agent by acting on the exact problem first: keep a processed set of thread ids, mark each duplicate set merged before moving to the next, and halt with a named blocker after the same flagged post appears in three merge attempts, because that post is anchoring the set the agent cannot finish. 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.