## TL;DR
Fix this in the answer library evidence set by acting on the exact message first: attach the latest penetration test attestation letter showing a test date inside the last 12 months, update every answer that cites the test date, and schedule the next refresh before the new letter ages out. 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.

```text
stale answer error penetration test date older than 12 months
```

## Use this when
- The operation in the answer library evidence set fails with this exact message: stale answer error penetration test date older than 12 months.
- The same failure repeats on retry with unchanged inputs.
- A review, export or check 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 answer library evidence set, and copy the full message plus the questionnaire, answer or evidence item 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: attach the latest penetration test attestation letter showing a test date inside the last 12 months, update every answer that cites the test date, and schedule the next refresh before the new letter ages out. Verify: the cited test date is inside 12 months and the attestation letter is the newest one on file.
3. Check the neighbouring items that share the same config, template, feed or credential, 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 counts, decisions or alerts against the source in the answer library evidence set so a silent partial success is caught before sign off. Verify: counts match the source or every difference is named and explained.
5. Rerun the original operation in the answer library evidence set 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
a newer test was completed but its attestation never replaced the old one in the library, so answers kept citing a date that aged past the 12 month limit.

## Variant phrasings

### stale answer error penetration test date older than 12 months
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: how to fix stale answer error penetration test date older than 12 months fails
The how-to phrasing for the same failure in the answer library evidence set. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

### the answer library evidence set 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.

Compatibility: the answer library evidence set at current versions, plus the platform API or console the query names; no extra tooling beyond a text editor and the source system access needed to verify counts.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_PKx0x-T3-UVdG6Er-NUI4w