Troubleshooting
Connection lost while signing a PDF? Recover without duplicating requests
A connection error can occur during transfer, preview loading, saving a signature or final submission. These stages need different recovery steps. Start by keeping the tab open and reading the visible message rather than refreshing immediately.
DocAISign paid checkout is not currently enabled. Self-signing is free; check your available sends and the Pricing page before planning a request.
If upload or scan creation failed
For an interrupted file upload, restore a stable connection and use an offered Retry upload control. A file-size or format error needs a corrected input instead. Repeatedly submitting the same invalid file will not solve the problem.
Keep scan work in the current tab while investigating. Accepted photos and unsent work may be held in browser memory; refreshing, leaving or closing the tab can lose them. A leave warning is not a permanent backup.
If the preview failed to load
A blank or failed page preview is not proof that the source file is empty. Reconnect and use the offered preview retry. Wait until the intended page renders before placing fields or finalising signatures.
If the problem persists, compare the source in a PDF viewer. Record the visible error and page count without posting the private document or signing link in a public support discussion.
If your sender signature is visible but not saved
The editor can retain an unsaved signature after a failed save and show Retry saving. Keep the tab open, reconnect and use that control. Wait for the saved status before sending or self-finalising.
The editor also attempts to save pending work when connectivity returns, but do not assume every visible mark has reached the server. Check the status and any remaining retry message. Browser-held recovery does not promise offline signing or recovery after the tab is gone.
If the final submit result is uncertain
A lost response does not tell you whether the server completed the operation. DocAISign checks current state after uncertain completion in the editor and signer flows. Read the resulting page and state before creating a replacement request.
If you reach the signed completion page, inspect and download the result. If the existing request still needs action, use the controls and message offered there after reconnecting. Do not repeatedly create new uploads or invitations simply because one response was lost.
If the link has closed during recovery
Cancelled, declined or expired is a request state, not merely a network problem. Retrying the same closed link will not revive it. Contact the sender through a known channel for the current request and clarify which version should be used.
For a mistaken request, the owner must inspect the current state before correction. A new invitation does not automatically close an earlier one.
A recovery checklist
- Keep the current tab open while work is unsaved.
- Identify transfer, preview, save or final-submit failure.
- Restore connectivity and use the relevant retry control once.
- Check the existing request state before creating another request.
- Save the completed PDF and audit when completion is confirmed.