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.

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