• INTEGRATIONS AND DEVELOPER API • SETUP GUIDE

How to Troubleshoot Google Sheets Sync Errors

By Rivio Support Team
2 min read

What you will achieve in this guide

Follow this step-by-step documentation to configure custom B2B registration forms, approval workflows, and customer tagging.

EXPECTED SETUP TIME 5-10 Minutes
COMPATIBILITY All Shopify Themes & Plans
TECHNICAL DIFFICULTY Zero Code Required

Check Google authorization, spreadsheet selection, destination tabs, and logged sync errors when Shopify application rows do not reach Sheets.

Before you begin

Use the intended service account and select the destination list, channel, spreadsheet tab, or endpoint. Decide whether you are testing a new-submission event or an approval event, and use a clearly identifiable test application.

Locate the failed part of the connection

First verify that the application exists and is not Spam. Then check the Google account, connection state, selected spreadsheet link, and destination tab. An authorization or destination problem can prevent the background row sync while the application itself remains received.

Sync errors are caught and logged in this release. If the app does not expose the needed log detail, give support the submission reference and time. Test a fresh application after correcting the connection; historical backfill is not established by this setup.

Reference and examples

Symptom Check Action
Reconnect banner Old Google scope Reconnect with drive.file.
Sheet opens but wrong tab Selected sync tab Choose and save the intended tab.
Permission lost Connected account and selected file Reconnect/select the authorized file.
Submission absent everywhere App inbox Diagnose receipt before Sheets sync.
Received but no row Spam status and sync logs Correct connection, test fresh data, and report unresolved error.

Diagnose and resolve the problem

  1. Confirm the test application exists in Submissions and is not Spam.

  2. Open Google Sheets settings and inspect connection status or a reconnect banner.

  3. Check the displayed spreadsheet name and link, then verify the selected tab still exists.

  4. Reconnect Google if authorization is outdated or revoked.

  5. Review available sync errors or contact support with the submission reference and time.

  6. Submit a fresh test and verify one expected row reaches the configured destination.

Example

Check a known test application's reference against the configured sheet and tab. If access was revoked, reconnect and submit a fresh test rather than assuming historical rows are replayed.

Expected result

The new test reaches the intended destination; unresolved errors can be reported with reference and time.

Limits and important behavior

  • Sync errors are caught and logged in the current release.
  • The applicant’s submission can succeed even when a background integration fails.
  • Do not assume retry, historical backfill, or approval-row update behavior unless it is explicitly exposed by the integration.

Troubleshooting and verification

If data does not reach the destination, confirm the application exists and is not Spam, then check the connection, event, and selected destination. Email-marketing services need an applicant email. Background failures do not undo a received submission.

Screenshots to add

Screenshot placeholder: Capture the relevant app screen for “How to Troubleshoot Google Sheets Sync Errors” after completing the setup. Show the controls used to confirm the test application exists in Submissions and is not Spam. Add a second screenshot showing the result of this check: Submit a fresh test and verify one expected row reaches the configured destination. Use dummy applicant details and mask any secrets.

Related guides