A document came back instead of releasing

A document you finished redacting has not released and is waiting for a person. That is the verification step doing its job rather than something going wrong.

What happened

After you finish redacting, the output is examined independently for anything that should have been withheld and was not. That check does not rely on the editor's record of what you applied; it reads the file that would actually go out.

If the check is clean, the document can move on toward Ready for Release. If it is not clean, the document is held.

How to deal with it

1. Open the document from the request's Case/Media tab.
2. Read what verification flagged.
3. Look at each flagged item in the document itself rather than deciding from the summary.
4. Redact anything that should have been caught.
5. Finish the session. It goes back through verification.

If you think the flag is wrong

Verification errs toward holding things back, so a flag you disagree with is not unusual. A name that belongs to a public official acting in their role is the classic case: the pattern matches, the withholding does not apply.

You are entitled to decide it should be released. Record why in an internal note before you do. That note is what explains the decision if the release is questioned later, and it costs a minute now against a great deal later.

What you cannot do

There is no setting that releases a document with an unclean verification, and no permission that overrides it. This is deliberate: the product defers to a person rather than releasing material it cannot verify.

If a document is genuinely stuck, the route is to resolve what was flagged, not to look for a way around the check.