Diagnose GoPaperless Agent
Locate failures across the application, Agent, account, signing route and validation; reconcile before signing again.
Diagnose GoPaperless Agent
- Symptom and failure point
- Transaction reference and time
- Reconcile before resubmitting
When Adobe reports UNKNOWN
Retain the exact document and validation time; inspect Signature Validation Status components. Review certificate chain, revocation sources, connectivity and time policy with the integration team. Do not disable checks to turn UNKNOWN into valid.
Troubleshoot by symptom
If the table is wider than its frame, scroll horizontally to see all columns; use arrow keys when the table region has focus.
| Symptom | Check | Next action |
|---|---|---|
| Installation fails | Package source, permissions and OS warnings | Stop for unexpected source/signature and contact IT. |
| Sign-in fails | Enabled method, network and message | Check the account; never send passwords to support. |
| No certificate | Account, issuance and Refresh | Check CA process and signer permissions. |
| Waiting for approval | Phone, route and request | Review the document before approval; reconcile a timeout. |
| Response lost | Transaction reference, time and source status | Do not resubmit signing automatically; establish the result. |
| Validation fails | Subject, trust chain and document changes | Keep the result for investigation; do not disable validation. |
MessageBox notifications
The source distinguishes important notifications, warnings/reminders and success confirmations. Read the message to identify the transaction and required action; color or an icon does not replace business status.
Source documentation: GoPaperless Agent · Quantera
Request support
- Provide OS, Agent and application versions and reproduction steps.
- Share the time, transaction reference if available and a privacy-filtered error message.
- Retain source and output documents for internal comparison; do not publish real records.