New article
Recently updated
Troubleshooting corrupted documents triggered by a tamper flag
Who is this article for?
Users responsible for managing documents.
IT Administration permissions are required to resolve the issue.
A tamper flag error signals a potential document integrity issue. Resetting this flag may trigger a secondary error: “Failed to load .pdf”, usually caused by a missing or corrupted file.
This article explains what these errors mean and provides recovery steps for both cloud and on-premises environments.
1. Issue
When a document shows a tamper flag error, it indicates that the system detected a potential integrity issue. Resetting the tamper flag can sometimes lead to a secondary error: “Failed to load .pdf”.
This typically means the document file is corrupted or inaccessible.
2. Solution
2.1. Hosted customers
To resolve the issue, create a new document or upload as a new revision if you have access to a local copy.
If no previous revision exists and no local copy if available, open a ticket with the following information:
- Document ID
- Timestamps
2.2. On-premise customers
To resolve the issue, create a new document or upload as a new revision.
Alternatively, you can restore the document database. This requires IT Administrator access and knowledge of your backup system.
If your organisation chooses this resolution route, they'll need to:
Restore a backup of your system.
Locate the file by Document ID in the restored environment.
Export the file.
Reupload it to the active system.
Restart application pool and services.
Run Document Automation tasks to verify integrity.