Signed PDF, Drive file or Sheet row is missing
Trace missing signed PDFs, Drive files and Sheet rows through the correct completion state, configuration and Google access path.
Reviewed 2026-10-30 · Formesign guides
Locate the Formesign response first, then follow the specific output path that is missing. A PDF, a saved Drive file and a response Sheet row each have their own configuration and access requirements.
Check the source response
Open the intended form and find the submission by its request details and date. Confirm that the person submitted the request rather than only opening or saving a draft. If the response is missing entirely, verify the shared link and form copy used for collection.
For a signing workflow, inspect required signers. An incomplete workflow can have a stored response without a final signed PDF. Follow workflow troubleshooting when a signature remains pending.
Find the missing output
| Missing item | Check |
|---|---|
| Signed PDF | Required-signature completion, generated output and the matching signed record |
| Drive file | Save to Google Drive configuration, selected pages, folder location and sharing permissions |
| Google Forms linked-Sheet row | Whether the response is forwarded to that Google Form and the Form's linked destination |
| Formesign report Sheet row | The report's own Link to Sheets connection, selected columns and sensitive-field choices |
| Emailed attachment | Recipient-specific notification settings and final PDF availability |
Check Drive access
Use a folder in My Drive. The current save setup does not support Shared Drive folders. If an organization blocks the service address shown in the error, ask its administrator to review that restriction.
An active saving badge means the connection is configured; inspect the individual response's sync status and the actual folder. Changing a destination should not be assumed to move previous files. See Drive setup.
Check spreadsheet content
Open the correct spreadsheet and tab. Remove an accidental filter or inspect hidden columns before concluding data is absent. A PHI-marked field can be excluded by the report export configuration; do not enable sensitive output without checking the destination's access.
Avoid repeatedly creating new connections before recording where the existing one points. After correcting the configuration, use a synthetic submission to establish the expected row or file. If historical responses remain absent, ask support which recovery or resync action is supported rather than assuming a new test backfills the archive.