## TL;DR
Break the loop for redact a call transcript before sharing a summary by giving the agent a done check it cannot argue with: before starting, look for an existing completed output for this exact call id and task, skip if one exists, and cap attempts at two with the failure reason recorded, because the agent kept re-running the same task on the same call and each run reproduced the same output or the same failure. Start with the full transcript text and the redacted copy prepared for sharing, and the agent run log for the step where it stopped, work on one affected call, record, or run first, and prove the fix there before running the full set. Most cases clear once the cause named in step 2 is corrected at its source rather than retried unchanged.

```text
agent loop detected: repeating the same call summary task to redact a call transcript before sharing a summary error loop failure
```

## Use this when
- You see this exact message or symptom: agent loop detected: repeating the same call summary task to redact a call transcript before sharing a summary error loop failure
- One run, record, call, or object is affected and you can name it
- A retry without changing anything reproduces the same result

## Not for this skill when
- The system fails with a different message and none of the signals here appear
- Nothing has failed yet and you are doing first time setup or general planning
- Every service from this vendor is down for all users, which is a vendor outage to wait out first

## Steps
1. Reproduce the failure once using the full transcript text and the redacted copy prepared for sharing, and the agent run log for the step where it stopped, and record the time, the workspace or account, and the one item it names. Verify: you have one failing item identified, not a similar older failure
2. Inspect the full transcript text and the redacted copy prepared for sharing. Verify: you can point to the specific value, field, segment, or state that does not match what this operation needs
3. Apply the fix at that source: Break the loop for redact a call transcript before sharing a summary by giving the agent a done check it cannot argue with: before starting, look for an existing completed output for this exact call id and task, skip if one exists, and cap attempts at two with the failure reason recorded, because the agent kept re-running the same task on the same call and each run reproduced the same output or the same failure. Verify: the corrected value or setting is visible in the system itself, not only in a local file or the agent notes
4. Re-run the original operation on the single affected item first. Verify: that one item completes with no trace of the failure described above, and no person, company, or pricing name from the original survives anywhere in the redacted body text
5. Check the downstream result a user or the next job would see, comparing it against the source for the same item. Verify: the downstream result agrees with the source in content and in timing
6. Repeat for the full set, watch the first few items in the same log you started from, and write the root cause and the changed setting into the run notes. Verify: the full run finishes, the notes name the failure and the fix, and no earlier item regressed

## Variant phrasings
### agent loop detected: repeating the same call summary task to redact a call transcript before sharing a summary error loop failure
The subject-first phrasing of the same failure. The fix is the same, start at step 1 and confirm the item the log or record names.
### Tool-first phrasing of this failure
The phrasing searchers use once they know which system raised it. It is the same underlying problem, not a separate bug.
### Why does this keep happening after a retry
The repeat-occurrence phrasing. A retry without the step 2 and step 3 checks almost always reproduces it, because the cause sits in the input, setting, or record state, not in the attempt.

Compatibility: transcript tool exports and API at current versions, plus the CRM or sharing destination the task names; the steps assume the run can be resumed per call rather than only as a whole batch.

## Why it happens
The loop forms when completion is judged by the agent own last action instead of by the destination state. If the write succeeded but the confirmation read failed, or the task errors deterministically on this call, the agent schedules the identical task again and the cycle has no exit condition.

## Provenance

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