how to fix evidence request error auditor document not in approved library fails
Fixes this security questionnaire failure. Fix: Ask the document owner to publish the auditor document into the approved library with an owner name and expiry date, then cite the library copy in the questionnaire instead of the audit folder copy. Use when the exact error in the title blocks the workflow it names. Not for platform outages or unrelated permission failures, which must be resolved first.
TL;DR
Fix this in the evidence request workflow by acting on the exact message first: ask the document owner to publish the auditor document into the approved library with an owner name and expiry date, then cite the library copy in the questionnaire instead of the audit folder copy. 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.
evidence request error auditor document not in approved libraryUse this when
- The operation in the evidence request workflow fails with this exact message: evidence request error auditor document not in approved library.
- 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
- Reproduce the failure with the smallest scope that still shows it in the evidence request workflow, 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.
- Apply the specific fix for this error: ask the document owner to publish the auditor document into the approved library with an owner name and expiry date, then cite the library copy in the questionnaire instead of the audit folder copy. Verify: the questionnaire cites a library item whose status reads approved and whose expiry is in the future.
- 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.
- Compare the result counts, decisions or alerts against the source in the evidence request workflow so a silent partial success is caught before sign off. Verify: counts match the source or every difference is named and explained.
- Rerun the original operation in the evidence request workflow 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.
- 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 document lived only in the audit working folder, which the approved library and the questionnaire tooling cannot cite, so the request could not be satisfied as filed.
Variant phrasings
evidence request error auditor document not in approved library
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 evidence request error auditor document not in approved library fails
The how-to phrasing for the same failure in the evidence request workflow. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.
the evidence request workflow 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 evidence request workflow 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/pstq8pReKrwHZhRUPHe6lWCQ