π΅οΈ Monitoring errors with the Errors sync tab
The "Errors sync" tab helps you monitor and manage issues that may occur during synchronization between Shopify and Airtable. It's your go-to place to understand what went wrong and how to fix it.
How the "Errors sync" tab works
- SyncBase automatically creates a tab called
Errors sync. - Do not delete it β itβs essential for tracking sync issues.
- Each error is represented by one record.
- A record includes: Error type, Linked Airtable record, Process ID, Timestamp...
What to do when an error occurs
- Check if the error resolved itself
Example: If an order had an invalid shipping address and you corrected it, the error may have already disappeared automatically.
- Review the error details
- Look at all the fields in the error record.
- Identify the operation that caused the issue.
- Check the
Error causefield
- It usually gives a clear explanation of the issue.
- Most of the time, it also tells you what needs to be corrected.
- Still stuck?
- Contact us directly via the live chat or at support@syncbase.app . Weβre happy to help.
List of errors
INVALID_PERMISSIONS_OR_MODEL_NOT_FOUND
π Cause: Usually this means that there's been an attempt to access or modify a record that does not exist anymore. It can happen when we receive a Shopify update but the related record got deleted.
Value is invalid JSON
π Cause: When it comes to metafields, this usually means the value you're entering doesn't match the format expected by Shopify.
β Solution: The easiest way to understand the correct format is to do the reverse:
- Add a value directly in Shopify.
- Save it.
- Check how that value appears in your synced Airtable base.
This will show you the format Shopify expects, so you can replicate it when editing from Airtable.
AMBIGUOUS_FIELD_NAMES
π Cause: You're trying to create a field with an already existing name (a synced or unsynced column).
β Solution: Just try another name
Access denied for field-name field
- Example: "Access denied for fulfillmentOrders field"
π Cause: SyncBase is missing one or several access scopes. It means that Shopify does not allow us to access some data for your store through the API.
β Solution: Contact us on the live chat and copy paste the error(s) so we know which access scopes are missing. We will then send to you a Shopify link, and you will be able to authorize missing access scopes.
Handle ' handle-name' already in use. Please provide a new handle.
- Example: "Handle 'my-super-handle' already in use. Please provide a new handle."
π Cause: You are using a handle that is already in use. Shopify does not allow you to have the same handle for several products. It often happens when you copy-paste Products records.
β Solution: Choose a different handle.
π In order to spot your duplicates handles and fix them, follow this guide.
Missing column
π Cause: there is a missing column in one of your tabs. It can happen because you accidentally delete it, or because you create something new (new location, new metafield, new field for a Metaobject definition...) in Airtable.
β Solution: Contact us on the live chat and copy paste the error(s) so we know which column(s) are missing.
TOO_MANY_RECORDS_IN_BASE
π Cause: it means that you've reached your max number of records Airtable authorize in your plan.
β Solutions: you can upgrade your Airtable plan in order to get more records allowed per base. Or you can limit data you synchronize (eg. remove Customers from your synchronization) between your store and Airtable.
Failed to retrieve a correct Product ID from record
π Cause: the value in the Product ID column is invalid. This happens when a record in the Products table is updated but contains an empty or duplicate Product ID. Without a valid Product ID, the sync cannot continue and throws an error.
This issue often occurs during bulk product creation from Airtable: multiple new records are created, but some fail to generate a corresponding product in Shopify. As a result, those records contain data for fields like Title, but the Product ID remains empty because the product was never created successfully in Shopify.
β Solution: Identify records with missing or duplicate Product IDs, and re-run the creation process for those records.
The variant 'Default Title' already exists
π Causes:
- A variant is being created with the same value as an existing one (you can't have two variants with exactly the same value for the same Product).
- A variant is being created with a
Variant namefield filled in manually (this field is automatically managed by Shopify).
β
Solution: create a new variant with unique values, and leave the Variant name field empty so Shopify can handle it.
Updated on: 16/09/2025
Thank you!