Locate the missing record at its source
Write down the form, approximate submission time and a safe record reference. Inspect the form’s own results before treating the sheet as the source of truth. A response absent from both places is a different problem from a stored response that never reached its destination.
Yay! Forms’ Inbox guide describes field filtering and a complete-only view. Check whether the current view excludes the entry. Removing an appropriate filter for inspection is not the same as changing collection rules or declaring an incomplete response usable. Never delete a record to troubleshoot delivery.
Compare the intended destination with the configured one
The Sheets setup guide uses Integrate → Google Sheets → Set up, a selected Google account, and either a new spreadsheet or an existing spreadsheet URL. Compare those identities with the destination you are reading. Similar sheet titles are not proof that they are the same file.
| Observation | Next read-only check | What it does not prove |
|---|---|---|
| Stored response; no visible row | Confirm exact file, tab and view/filter. | That the provider lost the data. |
| Integration attempt failed | Inspect its error and configured destination. | That resending will fix the underlying problem. |
| Attempt reported successful | Match the received row to the response reference. | That the row is in the correct reporting view or has correct columns. |
| No matching attempt found | Check connection state and relevant execution conditions. | That it is safe to send every historical response again. |
Read the log before using its resend action
Yay! Forms documents Integration → Logs, successful and failed entries, and details under Actions. Its log guide also exposes a separate resend operation. Reading details and resending are different actions: the latter may create another row or trigger downstream work.
For an uncertain delivery, reconcile the original attempt with the destination first. If a correction and resend are appropriate, authorize the specific record, retain its reference, and check the resulting row once. A repeated click is not evidence that the first transmission failed. Escalate unresolved access or service errors with a redacted record reference, not private response text or credentials.
Understand what the integration test sends
The Sheets guide says its test uses the last valid completed response and does not mark that response as sent in the integration. It is therefore not a harmless synthetic ping. Inspect the data and destination before using it; do not accidentally transmit a customer record to a test sheet.
Finish with a small reconciliation: intended response reference, observed delivery attempt, destination row and remaining uncertainty. If manual export is the temporary approved route, record the cutoff and avoid later double-counting those rows. See the export fixture for checking what actually arrived.
References and evidence limits
Product documentation describes the provider’s stated behavior, not our hands-on results. Worked records are fictional; methodological guidance does not certify a questionnaire or its findings.
- Yay! Forms Google Sheets connection — checked 2026-10-02
- Yay! Forms integration logs — checked 2026-10-02
- Yay! Forms response inbox — checked 2026-10-02