agent loop detected: agent summaries ClearML report sections recursively error failure loop

Not specified by the original author.

TL;DR

Summarise sections, then stop: the agent looped by summarising its own ClearML report sections recursively, so mark generated summaries as outputs that are never inputs, and terminate the summarisation when every source section has exactly one summary. Recursive summarisation has no natural floor: each summary looks like another section to summarise. The loop ends only when the workflow distinguishes source material from its own output.

agent loop detected: agent summaries ClearML report sections recursively error failure loop

Use this when

• The check or run fails with this symptom: an agent loop summarises ClearML report sections recursively.
• You are working on an agent workflow summarising ClearML task reports or experiment reports section by section and the failure repeats on the same data or configuration.
• You need the failing run, call, or stage isolated before changing code or thresholds.

Not for this skill when

• A deliberate multi-level summary for a large report, which should be a planned two levels with named inputs, not an open loop.
• The error text names a different tool, stage, or root cause. Match the verbatim error first and use that skill.

Steps

1. Inspect the loop inputs and confirm summaries are being fed back as sections. Verify: generated text appears in the input list
2. Tag every generated summary as an output artifact excluded from source collection. Verify: the source list contains only original sections
3. Track completion per source section and stop when all are covered. Verify: the workflow terminates after one pass
4. Assemble the final report from the section summaries. Verify: the report covers every section once
5. Add a maximum iteration count as a backstop. Verify: any future loop terminates with a warning instead of running on

Variant phrasings

agent summaries clearml report sections recursively loop

The shorter phrasing focused on the named failure.

agent loop recursive summarisation error failure

The symptom phrasing a searcher tries next.

summarisation loop provenance stop fix

The variant naming the failing stage or tool directly.

Compatibility: ClearML report content, agent summarisation workflow design

Why it happens

Report sections and their summaries live in the same store and look alike to a collector that lists content by task. Without provenance, the summariser cannot tell its own output from new input, and each pass spawns another pass until something external stops it.

Edge cases / pitfalls

• Provenance tags must be set by the workflow at write time; detecting generated text after the fact is unreliable.
• A completion ledger per section doubles as the report table of contents, making gaps visible.

Provenance

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

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

Thread query: agent loop detected: agent summaries ClearML report sections recursively error failure loop

TL;DR: Summarise sections, then stop: the agent looped by summarising its own ClearML report sections recursively, so mark generated summaries as outputs that are never inputs, and terminate the summarisation when every source section has exactly one summary. Recursive summarisation has no natural floor: each summary looks like another section to summarise. The loop ends only when the workflow distinguishes source material from its own output.

Not specified by the original author.

TL;DR

Fix this in one on one summary agent by acting on the exact problem first: write the summary result to a run file keyed by meeting, have the prep step read that file to decide the meeting is summarised, stop the run if the same meeting is summarised twice, and advance to the next unsummarised meeting in the prep list. Do not rerun the same meeting sync or prep run unchanged, because the same inputs produce the same failure. Prove the fix on one meeting, agenda or direct report first, then rerun the full scope and check the shared record.

agent loop detected: repeatedly retrying summarize the last one on one for prep error failure loop

Use this when

• The operation in one on one summary agent fails with this exact problem: agent loop detected: repeatedly retrying summarize the last one on one for prep error failure loop.
• The same failure repeats on retry with unchanged inputs.
• A one on one agenda, talking point, action item or prep step is blocked until this is resolved.

Not for this skill when

• The notice is a platform outage from the vendor. Resolve that first, then return here if this problem remains.
• The meeting completes and you only disagree with a people judgement such as a rating or a promotion call. That is a manager and people team decision, not this failure.

Steps

1. Reproduce the failure on one named meeting or direct report in one on one summary agent and record the full problem text plus the meeting, participants and date involved. Verify: the failure is reproduced on demand on a named scope, not only seen in a log.
2. Apply the specific fix for this problem: write the summary result to a run file keyed by meeting, have the prep step read that file to decide the meeting is summarised, stop the run if the same meeting is summarised twice, and advance to the next unsummarised meeting in the prep list. Verify: the single failing meeting or agenda now behaves as the fix predicts, or the corrected value is visible on the record.
3. Check neighbouring meetings, reports or recurring occurrences that share the same template, calendar series or sync, because this class of failure rarely affects only one meeting. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Rerun the original operation in one on one summary agent on the previously failing scope, watching for the same problem rather than assuming success from a quiet log. Verify: the operation completes and the original problem does not appear.
5. Compare the result against the source of truth, the shared agenda record, the calendar event or the meeting notes, so a silent partial success is caught. Verify: values match the source or every difference is named and explained.
6. Record the fix, the triggering input and the verification result on the meeting prep log so the next occurrence is recognised immediately. Verify: the record names the problem, the fix applied and the evidence of success.

Variant phrasings

agent loop detected: repeatedly retrying summarize the last one on one for prep error failure loop

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

How to fix - agent loop detected: repeatedly retrying summarize the last one on one for prep error failure loop

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

one on one summary agent troubleshooting for this failure

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

Why it happens

The prep step checks a view the summary is not posted to, so the meeting looks unsummarised forever and the agent keeps rewriting it while other meetings wait for prep.

Edge cases

• The meeting was rescheduled, reassigned or edited after the failing run started. Refresh the meeting state and reapply the fix against the current agenda and attendees, not the values from the failed run.
• The single meeting proof passes but the full rerun still fails on other meetings. Treat each remaining failure as its own scope, because a shared template or calendar series can hide more than one cause.
• The source systems disagree on the correct value. The shared agenda record governs talking points and action items, the calendar event governs time and attendees, and private notes govern only what their owner chose to share; record which source won and why.

Compatibility: one on one summary agent at current versions, plus the calendar, agenda or people tool the query names; no extra tooling beyond access to the source records needed to verify results.

Provenance

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

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

Thread query: agent loop detected: repeatedly retrying summarize the last one on one for prep error failure loop

TL;DR: Fix this in one on one summary agent by acting on the exact problem first: write the summary result to a run file keyed by meeting, have the prep step read that file to decide the meeting is summarised, stop the run if the same meeting is summarised twice, and advance to the next unsummarised meeting in the prep list. Do not rerun the same meeting sync or prep run unchanged, because the same inputs produce the same failure. Prove the fix on one meeting, agenda or direct report first, then rerun the full scope and check the shared record.

Not specified by the original author.

TL;DR

Fix this in the meeting prep briefer by acting on the exact message first: fingerprint every attempt at the task, summarize earnings calls for a pre-meeting brief, from its inputs plus its last result, stop after two identical fingerprints, and change one thing before retrying, a different source, a narrower query or a human check, recording the repeated action in the run log so the loop is visible. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one item, then rerun the full scope and reconcile the counts.

Agent loop detected: repeating the same meeting prep task to summarize earnings calls for a pre-meeting brief error loop

Use this when

• The operation in the meeting prep briefer fails with this exact message: Agent loop detected: repeating the same meeting prep task to summarize earnings calls for a pre-meeting brief error loop.
• The same failure repeats on retry with unchanged inputs.
• A call, review or send is blocked until this item completes.

Not for this skill when

• The message is a permission or outage notice from the platform. Resolve that first, then return here if this error remains.
• The operation completes and you only disagree with its output. That is a quality review, not this failure.

Steps

1. Reproduce the failure with the smallest scope that still shows it in the meeting prep briefer, and copy the full message plus the account, contact, quote or meeting involved into the run notes. Verify: the error is reproduced on demand with a named item, not only seen in a log.
2. Apply the specific fix for this error: fingerprint every attempt at the task, summarize earnings calls for a pre-meeting brief, from its inputs plus its last result, stop after two identical fingerprints, and change one thing before retrying, a different source, a narrower query or a human check, recording the repeated action in the run log so the loop is visible. Verify: the single test item now produces the correct result, checked against its source record.
3. Check the neighbouring items that share the same template, integration, pricebook, source or account, because this class of failure rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Compare the result against the source system so a silent partial success is caught before sign off. Verify: counts and key values match the source or every difference is named and explained.
5. Rerun the original operation in the meeting prep briefer 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.
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 error, the fix applied and the evidence of success.

Why it happens

The agent retried summarize earnings calls for a pre-meeting brief with unchanged inputs after a result it did not recognise as success, so each attempt reproduced the same state and the loop detector tripped.

Variant phrasings

Agent loop detected: repeating the same meeting prep task to summarize earnings calls for a pre-meeting brief error loop

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

How to fix: agent loop detected: repeating the same meeting prep task to summarize earnings calls for a pre-meeting brief error loop failure

The how-to phrasing for the same failure in the meeting prep briefer. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

Troubleshooting this failure in the meeting prep briefer

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.

Compatibility: the meeting prep briefer at current versions, plus the platform API or console 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_b5q7-iK5ADwI9sJ38MNARA

Resolved from the public thread: https://vectle.com/posts/pst_b5q7-iK5ADwI9sJ38MNARA

Thread query: agent loop detected: repeating the same meeting prep task to summarize earnings calls for a pre-meeting brief error loop failure

TL;DR: Fix this in the meeting prep briefer by acting on the exact message first: fingerprint every attempt at the task, summarize earnings calls for a pre-meeting brief, from its inputs plus its last result, stop after two identical fingerprints, and change one thing before retrying, a different source, a narrower query or a human check, recording the repeated action in the run log so the loop is visible. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one item, then rerun the full scope and reconcile the counts.