Pushrow for Google Sheets is designed to run reliably in the background without manual intervention. But occasionally things go wrong — a sync stops working, data isn’t appearing in your Sheet, or an error shows up in the logs. This guide covers the most common issues and how to resolve them.
Step 1 — Check the Sync Logs
The first place to look when a sync isn’t working is Pushrow → Sync Logs. Every sync attempt is logged with a status (success or error) and an error message if applicable. The log tells you exactly what happened and when.
Common log error messages and what they mean:
- ‘Invalid credentials’ or ‘Token expired’ — your Google OAuth token needs to be refreshed
- ‘Spreadsheet not found’ — the Google Sheet was deleted or moved
- ‘Permission denied’ — the Google account lost access to the Sheet
- ‘Rate limit exceeded’ — too many API requests in a short period
- ‘Plugin not active’ — an integration plugin (Gravity Forms, WooCommerce, etc.) was deactivated
Common Issue 1 — Google Account Disconnected
Google OAuth tokens expire and sometimes need to be re-authorized. If your syncs suddenly stop working after a period of working correctly, this is often the cause.
Fix: Go to Pushrow → Settings and click Reconnect Google Account. Go through the OAuth flow again to refresh your token. Your sync jobs will resume automatically.
Common Issue 2 — Redirect URI Mismatch
This typically occurs after a domain change, SSL migration, or WordPress URL change. If your site URL changed since you set up the OAuth credentials in Google Cloud Console, the redirect URI no longer matches.
Fix: Go to Google Cloud Console → APIs & Services → Credentials. Edit your OAuth client and update the Authorized redirect URI to match your current site URL. Then reconnect your Google account in Pushrow.
Common Issue 3 — Sheet or Tab Deleted
If someone deletes the Google Sheet or tab that a sync job is pointing to, new syncs will fail with a ‘spreadsheet not found’ error.
Fix: Create a new Sheet or restore the deleted one, then edit the sync job in Pushrow and update the destination Sheet. All future syncs will go to the new destination.
Common Issue 4 — Field Mapping Broken After Plugin Update
Occasionally, a plugin update (WooCommerce, Gravity Forms, etc.) changes field names or data structures. If your field mapping references a field that no longer exists, those columns will sync as empty.
Fix: Edit the sync job and refresh the field list. Re-map any fields that show as unmapped or missing.
Common Issue 5 — Data Appearing in Wrong Columns
If data is appearing but in the wrong columns, the field mapping doesn’t match your Sheet’s column structure.
Fix: Edit the sync job and review the field mapping. Verify that each field maps to the correct column header. Run a test sync to confirm.
Common Issue 6 — Duplicate Rows
Duplicate rows can occur if a sync job is accidentally triggered twice for the same event, or if you ran a bulk sync on data that was already in your Sheet.
Fix: Review your sync job settings to ensure there aren’t duplicate trigger configurations. For bulk syncs, use a date range to avoid reprocessing data that’s already been synced.
Getting Support
If you’ve worked through the troubleshooting steps above and your sync still isn’t working, reach out to PluginStack support at pluginstack.dev/contact. Include your sync log entries and a description of what you expected vs. what happened — this helps us diagnose the issue quickly.
Pushrow for Google Sheets is included in the PluginStack bundle — 6 premium plugins for a one-time payment of $99 (Solo) or $179 (Agency). Lifetime updates included. No recurring fees.
→ Get PluginStack at pluginstack.dev/pricing