## TL;DR
Fix this in AWS Config evidence agent by acting on the exact problem first: break the loop by stopping after the third identical 403 response, record the snapshot and the permission error as the blocker, fix the Config read permission, and resume from the saved checkpoint rather than requesting the snapshot again in a loop. Do not rerun the whole job or collection unchanged, because the same inputs produce the same failure. Prove the fix on one control, account or batch first, then rerun the full scope and reconcile the counts.

```text
loop detected - re-requesting the same snapshot after repeated 403s
```

## Use this when
- The operation in AWS Config evidence agent fails with this exact message or symptom: loop detected - re-requesting the same snapshot after repeated 403s.
- The same failure repeats on retry with unchanged inputs.
- An audit, evidence package or compliance review 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 an auditor judgment or a control design choice. That is a review discussion, not this failure.

## Steps
1. Reproduce the failure with the smallest scope that still shows it in AWS Config evidence agent, and copy the full message plus the control, account or item 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: break the loop by stopping after the third identical 403 response, record the snapshot and the permission error as the blocker, fix the Config read permission, and resume from the saved checkpoint rather than requesting the snapshot again in a loop. Verify: the smallest failing scope now completes, or the named control, account or item behaves as the fix predicts.
3. Check the neighbouring controls, accounts or items that share the same connection, mapping or owner, 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 AWS Config evidence 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 AWS Config evidence 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
An agent that treats a permission denial as a transient failure retries forever, because the request can never succeed until the permission itself changes.

## Variant phrasings

### loop detected - re-requesting the same snapshot after repeated 403s
The verbatim form searchers paste from the console, ticket or audit request. Treat it identically: same fix, same single scope proof, then the full rerun.

### How to fix - agent loop detected re-requesting the same AWS Config snapshot after repeated 403s
The how to phrasing for the same failure in AWS Config evidence agent. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

### AWS Config evidence 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 evidence was already sent to an auditor in the wrong state, correct the record with a dated note explaining what changed, rather than silently replacing files in the package.
- If two settings or mappings 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: AWS Config evidence agent at current versions, plus the admin console 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_Egv945aw_iP675RAWGHWBg