Documents
Monitor processing jobs and retry failures
Understand queued, running, completed, and failed remediation jobs and retry only when it is safe.
- For
- Document owners and operators
- Typical time
- 3 minutes
Before you start
- At least one uploaded document
Procedure
Step by step
Open Processing jobs
Use the app's More menu or a failed document's View history link to inspect recent work.
Read the terminal state
Queued and running jobs should progress automatically. Succeeded jobs have version outputs. Failed jobs display sanitized, user-safe context.
Retry once after a transient failure
Use Retry when the UI offers it. The system creates a new processing attempt without pretending the failed attempt succeeded.
Escalate repeated failures
If the same file fails again, contact support with the document title, approximate time, and visible error. Do not email confidential source files.
Common causes
Damaged files, unsupported structures, malware-scan failures, parser limits, provider failures, or worker resource limits can stop processing. Raw system errors and document content are intentionally not exposed in the browser.
Related guides
- Upload and remediate a documentUpload a PDF or DOCX, follow processing, and understand the outputs created by automated remediation.
- Get support and report an accessibility barrierSend enough context for a useful response without putting confidential documents or sensitive credentials into the contact form.
- Understand automation, conformance, and manual remediationKnow what DocAccessible automates, what still requires human validation, and when exact-layout manual PDF remediation is the right path.