Redaction does not take even though marked for redaction

[FionaTBK]

Hi all,

I have come across an instance where an area was marked for redaction and when a user went to create a copy of the file and apply redaction the area marked for redaction did not redact. 

Have any of you come across this before and identified what the problem is. No error message appeared. 

The user would have being using Adobe Pro 2020 but now has the Adobe cloud version. 

Thanks

Fiona

[Amal.]

Hi @FionaTBK 

Hope you are doing well and thanks for reaching out.

Would you mind sharing a small video recording of the steps you are doing to redact the PDF file?

Make sure you have the application updated to the recent version 23.03.20215, go to Help > check for updates and reboot the computer once.

Also check out the help page https://helpx.adobe.com/acrobat/using/removing-sensitive-content-pdfs.html and see if that works.

Regards

Amal

[FionaTBK]

Hi @Amal. ,

Thanks for responding to the post. 

The issue I'm describing appears to have happened with Adobe Pro 2020 and the account has been updated to the latest version of Adobe and I'm not able to replicate the issue. However, I do want to ascertain if this a technical issue that we need to be aware of or a "user" error. This happened about 3 times to a colleague. 

The steps that are followed though is that the document is marked for redaction and this is saved. A review is completed of the document to ensure that the document is appropriately marked and to identify if any other information should be marked. Once that has been completed the document is reviewed and any new suggested redactions approved. Once that has been completed the user goes save as and renames the file and saves it in a new folder. When the document was being saved it appeared to "loose" marked for redactions in one area of the document. 

When we followed the steps and went save as in the 2020 version it saved correctly and did not "loose" the redactions. 

Thanks

Fiona

[Amal.]

Hi there

We are glad to hear that the issue got fixed.

Feel free to contact us for any assistance required in the future.

~Amal