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

1. 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.

2. Review the error details

• Look at all the fields in the error record.
• Identify the operation that caused the issue.

3. Check the Error cause field

• It usually gives a clear explanation of the issue.
• Most of the time, it also tells you what needs to be corrected.

4. Still stuck?

Contact us directly via the live chat or at support@syncbase.app. We're happy to help.

List of errors

We’re working on a detailed list of common errors. For each error you'll find: 1) What it means 2) Why it happens 3) What to do to fix it

Structural errors

UNKNOWN_FIELD_NAME — column renamed or deleted

📌 Cause: A required column was renamed or deleted in your Airtable base. SyncBase can no longer find it, which breaks the sync for affected records.

✅ Solution:

• If the column was renamed: delete the column with the wrong name, then contact us via the live chat — we will rebuild and reconnect it for you.
• If the column was deleted: contact us via the live chat — we will recreate it with the correct properties.

Once rebuilt, run a Base Refresh from the Operations tab in the SyncBase app to repopulate the records.

UNKNOWN_FIELD_NAME — linked record field renamed or deleted

• Example: Unknown field name: "Order"

📌 Cause: A linked record field (such as Order) was renamed, deleted, or had its properties modified. SyncBase can no longer find it and cannot sync the affected records.

✅ Solution:

• If it was renamed: restore the original name exactly, then run a Base Refresh from the Operations tab.
• If it was deleted or properties were modified: delete the field entirely, then contact us via the live chat — we will recreate it with the correct linked field configuration.

Base is missing an essential column

• Example: Missing column: Cost per item

📌 Cause: A required column was deleted from one of your synced tables. SyncBase cannot write data to a field that no longer exists.

✅ Solution: Contact us via the live chat and let us know which column is missing. We will add it back from the admin panel, then run a Base Refresh to repopulate the records.

INVALID_VALUE_FOR_COLUMN — computed field or metaobject column

📌 Cause: Two possible causes:

• A synced field has a formula applied to it. SyncBase cannot write to computed fields.
• For Metaobject tables: an unsynced column does not have the - SyncIgnore suffix, so SyncBase is trying to write to it.

✅ Solution:

• Remove the formula from the synced field and keep formulas in non-synced columns only.
• For Metaobject tables: add - SyncIgnore to the end of any unsynced column name so SyncBase skips it.

👉 Adding a new unsynced column to a metaobject tab

INVALID_VALUE_FOR_COLUMN — linked record field conflict

• Example: Field "Order" cannot accept the provided value

📌 Cause: A linked record field was modified — its type was changed or it now points to the wrong table. SyncBase cannot write to it.

✅ Solution: Delete the conflicting linked field, then contact us via the live chat. We will recreate it with the correct linked field properties.

ROW_TABLE_DOES_NOT_MATCH_LINKED_TABLE

• Example: Record ID [...] belongs to table A, but the field links to table B

📌 Cause: A linked record field was modified and now points to the wrong table, creating a conflict.

✅ Solution: Identify the affected linked record fields, delete them, then contact us via the live chat. We will recreate them with the correct table links.

DUPLICATE_OR_EMPTY_FIELD_NAME

📌 Cause: SyncBase is trying to create a column with a name that already exists in your base — either because you added a custom column with the same name as a synced field.

✅ Solution: Rename your custom column in Airtable so it no longer conflicts with the synced column name, then retry.

INVALID_FILTER_BY_FORMULA

📌 Cause: A synced column used by SyncBase for filtering records was renamed, deleted, or had its type changed. SyncBase can no longer query the table correctly.

✅ Solution:

• If the column was renamed: restore its original name.
• If the column was deleted: contact us via the live chat so we can recreate it.
• If the type was changed: delete the field and contact us so we can rebuild it correctly.

ROW_DOES_NOT_EXIST

📌 Cause: A linked record reference is broken or stale — it points to a record that no longer exists.

✅ Solution: Run a Base Refresh from the Operations tab in the SyncBase app. If the error persists, run it again — it usually resolves after one or two refreshes.

Base already contains tables with names that would be created by this synchronization

• Example: Base already contains tables with names that would be created by this synchronization: Orders

📌 Cause: Your Airtable base already has a table with the same name SyncBase is trying to create, causing a conflict.

✅ Solution:

1. Open your Airtable base and find the conflicting table (e.g. Orders).
2. Rename it to something different (e.g. Orders - old).
3. Go to the SyncBase app → Operations tab and click Refresh for that table.

Base is missing an essential column

📌 Cause: There is a missing column in one of your tabs. This can happen because you accidentally deleted it, or because something new was added in Airtable (new location, new metafield, new field for a Metaobject definition).

✅ Solution: Contact us via the live chat and paste the error so we know which column(s) are missing. We will add them back for you.

INVALID_PERMISSIONS_OR_MODEL_NOT_FOUND (Record deleted in Airtable)

📌 Cause: Usually means an attempt was made to access or modify a record that no longer exists — typically when SyncBase receives a Shopify update but the related record was already deleted in Airtable. In rarer cases, it can indicate a token permissions issue.

✅ Solution: If the error appears in isolation and nothing else seems broken, it is safe to ignore — the record was likely already deleted. If the error repeats extensively or nothing is syncing, check your Airtable token status.

👉 Fixing a broken Airtable token status

Token & permissions errors

UNAUTHORIZED — Invalid authentication token

📌 Cause: SyncBase can no longer authenticate with your Airtable account. The token connected to SyncBase has expired, been deleted, or had its permissions changed.

✅ Solution:

1. Open the SyncBase app in your Shopify admin and go to the Settings tab.
2. Check the Airtable Token Status — if it shows as broken or inactive, follow the guide below.

👉 Fixing a broken Airtable token status

INVALID_PERMISSIONS — Sandboxing enabled

• Example: This request cannot be performed when sandboxing is enabled

📌 Cause: Your Airtable token has restricted permissions — an administrator has enabled sandboxing on the workspace, which prevents SyncBase from creating or updating certain columns.

✅ Solution:

1. Check if your Airtable workspace has sandboxing enabled by an admin.
2. If you are the admin: adjust the token permissions to give SyncBase full access to the synced base.
3. If you are not the admin: ask your Airtable workspace administrator to update the token settings.

👉 Airtable sandbox documentation

👉 Fixing a broken Airtable token status

Access denied for field-name field

• Example: Access denied for fulfillmentOrders field
• Example: Access denied for resourcePublications field. Required access: read_publications

📌 Cause: SyncBase is missing one or more Shopify access scopes. Shopify is blocking access to certain data for your store through the API.

✅ Solution:

1. Open the SyncBase app in your Shopify admin.
2. Look for a permission request popup — click Accept.
3. If no popup appears, contact us via the live chat and paste the error. We will send you a direct Shopify link to authorize the missing access scopes.

👉 What to do if my synchronization is not working

Airtable limit errors

TOO_MANY_RECORDS_IN_BASE

📌 Cause: You have reached the maximum number of records allowed by your current Airtable plan. Once this limit is hit, your base becomes read-only and SyncBase can no longer sync data.

✅ Solution — pick one of the options below:

1. Upgrade your Airtable plan — the simplest fix. Check your current usage in the bottom-left corner of your Airtable base.
2. Sync less data — remove data groups you don't need from your SyncBase sync settings, or use the SyncIgnore tag to exclude specific items.
3. Delete old records — for Orders or Customers tables, remove records older than a certain date to free up space.

👉 What to do if you reached Airtable's record limit

LIMIT_CHECK_TOO_MANY_RECORDS_IN_TABLE

📌 Cause: A specific table in your Airtable base has reached its record limit. SyncBase cannot add new records (such as new variants) until space is freed up.

✅ Solution — pick one of the options below:

1. Upgrade your Airtable plan — gives you a higher record allowance immediately.
2. Sync less data — remove data groups you don't need, or use SyncIgnore to exclude specific items.
3. Delete old records (Orders and Customers only) — remove old Orders or Customers you no longer need.

👉 What to do if you reached Airtable's record limit

FAILED_LIMIT_CHECK

📌 Cause: Your Airtable base has hit a structural limit — either too many columns (Airtable's maximum is 500 per table) or too many tables in the base. SyncBase cannot create new columns or tables until you free up space.

✅ Solution:

1. Open your synced Airtable base and check the number of columns in the affected tables (especially Products, Variants, Orders).
2. Delete any custom non synced columns you no longer use (do not delete synced columns)
3. If you are syncing Tables you don't need (e.g. Customers, Orders, Metafields) toggle those off from your SyncBase sync settings.
4. Not sure what to remove? Contact us via the live chat and we can review your setup together.

INVALID_MULTIPLE_CHOICE_OPTIONS

• Example: Cannot create more select options

📌 Cause: Airtable has a limit on the number of options allowed in a single-select or multi-select field. You have either hit that limit, or a value you entered does not match any existing option.

✅ Solution:

1. Find the select or dropdown field mentioned in the error in your synced Airtable base.
2. If you have hit the option limit: review existing options and remove any that are no longer in use.
3. If a value is invalid: make sure it exactly matches one of the existing options (case-sensitive).

Operations errors

Value must be a single line text string / CC status can't be blank

📌 Cause: Incorrect data format or a required field was left empty in Airtable.

✅ Solution: Check the affected records in your Errors sync tab. Make sure all required fields are filled in and that text fields contain the correct format — e.g. plain single-line text with no line breaks or special formatting.

Handle has already been taken

📌 Cause: Two or more items share the same Shopify handle. Handles must be unique across all products, collections, and variants.

✅ Solution:

1. Go to the affected table in Airtable (Products, Collections, or Variants).
2. Find the records sharing the same Handle value.
3. Edit one to make it unique (e.g. summer-sale → summer-sale-2025).
4. Go to the SyncBase app → Operations tab and click Refresh for the relevant table.

👉 How to fix duplicate handles

Handle 'handle-name' already in use. Please provide a new handle.

📌 Cause: You are using a handle that is already taken by another product, collection, or variant. This often happens when copy-pasting records.

✅ Solution: Choose a different, unique handle for the record.

👉 How to fix duplicate handles

Found 0 or more than 1 record for given Product ID

📌 Cause: There are duplicate records in your Airtable base with the same Product ID, or a Product ID is missing entirely. SyncBase needs exactly one record per Product ID to sync correctly.

✅ Solution:

1. Go to the SyncBase app → Operations tab and run a Base Refresh — this cleans up incorrect or stale IDs automatically.
2. After the refresh, check your Products table for any remaining duplicate records and delete the extras.

Failed to retrieve a correct Product ID from record

📌 Cause: The value in the Product ID column is invalid, empty, or duplicated. This often happens during bulk product creation from Airtable — some records fail to generate a product in Shopify, so the Product ID remains empty.

✅ Solution: Identify records with missing or duplicate Product IDs and re-run the creation process for those records. Running a Base Refresh from the Operations tab can also clean up stale IDs automatically.

Failed to retrieve a correct Variant / Customer / Order ID from record

📌 Cause: The ID column for a Variant, Customer, or Order record is either empty or contains an incorrect value. SyncBase cannot process that record without a valid ID.

✅ Solution:

1. Go to the affected table in Airtable and look for records with a missing or incorrect ID.
2. Go to the SyncBase app → Operations tab and run a Base Refresh — this will automatically populate the correct IDs from Shopify.

Missing Product ID for variant creation

📌 Cause: A variant was added in Airtable without following the correct creation process. The minimum required fields were not filled in at the moment of creation, so Shopify never created the variant and no Product ID was generated.

✅ Solution:

1. Delete the incomplete records in your Airtable Variants table.
2. Always fill in all required fields at the moment of creation — especially Product ID and all Option values set for that product.

👉 How to create a new variant from Airtable

The variant 'Default Title' already exists

📌 Cause:

1. A variant is being created with the same option values as an existing one — you cannot have two variants with exactly the same options for the same product.
2. The Variant name field was filled in manually — this field is automatically managed by Shopify.

✅ Solution: Create the variant with unique option values and leave the Variant name field empty so Shopify can handle it.

👉 How to create a new variant from Airtable

Already exists — high volume of variant creation errors

📌 Cause: A high volume of variant creation errors in a short period of time. This typically happens during bulk operations or when an automation is running at high speed, exceeding Shopify's API limits.

✅ Solution:

1. Review the error details in your Errors sync tab to identify what is blocking the process.
2. If running bulk operations: process in smaller batches to stay within Shopify's API limits.
3. If an automation is involved: review its trigger frequency and add delays if needed.

👉 Bulk operations guide

INVALID_ATTACHMENT_OBJECT — Invalid attachment object for field "Images"

📌 Cause: A video file was detected in your Airtable Images field. Shopify's Images field only accepts image files (JPG, PNG, WebP, etc.) — videos are not supported.

✅ Solution:

1. Go to the Products table in your synced Airtable base.
2. Check the Images field and remove any video files.
3. If you need to store videos, use a separate non-synced column.

A phone number is required to set the SMS consent state

📌 Cause: A customer record has SMS consent set but no phone number provided. Shopify requires a phone number before SMS consent can be saved.

✅ Solution: Check the affected record in your Customers table and make sure a valid phone number is entered before setting the SMS consent field.

Customer address cannot be blank

📌 Cause: A customer record is missing address information, or the name and address were not entered in the correct order. Shopify requires the customer's name to be present before the address.

✅ Solution:

1. Go to the Customers table in your synced Airtable base.
2. Find the affected record(s) in the Errors sync tab.
3. Make sure the customer's name is entered first, then the address — the order matters.

Expected one product but got 0

📌 Cause: SyncBase tried to update a product but could not find any matching record in Shopify. This usually means the product was deleted in Shopify, or the ID in Airtable is outdated.

✅ Solution:

1. Go to the SyncBase app → Operations tab and run an individual record refresh for that Product ID.
2. If the product was deleted in Shopify, you can safely delete the corresponding record in your Airtable base.

Operation is not supported for a combined listing parent product

📌 Cause: This operation is not supported for combined listing parent products in Shopify.

✅ Solution: No action needed — this can be safely ignored.

Throttled — Shopify API rate limit

📌 Cause: Too many operations were sent to Shopify in a short period, exceeding the API rate limit. This results in a large queue that appears to stall.

✅ Solution:

1. If running bulk operations: process in smaller batches and add delays between them.
2. If using Airtable automations: reduce trigger frequency.

👉 Bulk operations guide

Limit of 250 media per product reached

📌 Cause: You have hit Shopify's limit of 250 images or media files per product. Any additional uploads are blocked until the count is reduced.

✅ Solution:

1. Open your Shopify admin and go to the product hitting this limit.
2. Remove any duplicate or outdated images.
3. Keep the total number of media files at 250 or below per product.

The same publication was specified more than once

📌 Cause: A product or resource is being sent to the same Shopify sales channel or publication twice in the same operation, causing a conflict.

✅ Solution:

1. Check the affected product or collection record in Airtable for duplicate publication entries.
2. If you have an automation that triggers publishing, review its logic to ensure it does not fire twice for the same publication.
3. Remove the duplicate so each sales channel appears only once per record.

Value does not exist in provided choices

• Example: Value does not exist in provided choices: ["UK: D 1/2 - US: 2.25", ...]

📌 Cause: A value in your Airtable base does not match any of the allowed options defined for this metafield in Shopify. Shopify only accepts values from a predefined list, and values are case-sensitive.

✅ Solution:

1. Open your Shopify admin and go to Settings > Custom data to find the metafield definition mentioned in the error.
2. Review the list of allowed values for that metafield.
3. In your Airtable base, update the affected record so its value exactly matches one of the allowed options.
4. Once corrected, SyncBase will retry the sync automatically.

Owner subtype does not match the metafield definition's constraints

📌 Cause: A metafield is being applied to the wrong resource type — for example, a metafield defined for Products is being applied to a Variant, or vice versa. Shopify enforces strict owner type constraints on metafield definitions.

✅ Solution:

1. Open your Shopify admin and go to Settings > Custom data to review your metafield definitions.
2. Check which resource type (product, variant, customer, etc.) each metafield is defined for.
3. In your Airtable base, make sure each metafield is mapped to the correct table and resource type.
4. If needed, create a new metafield definition with the correct owner type in Shopify.

The specified location could not be found

📌 Cause: A Shopify location referenced in your sync (for example for inventory) no longer exists — it was deleted or renamed in Shopify.

✅ Solution:

1. Open your Shopify admin and go to Settings > Locations.
2. Verify that all locations referenced in your Airtable base are still active and correctly named.
3. If a location was deleted or renamed, update the corresponding references in your Airtable base.
4. Once corrected, SyncBase will retry the sync automatically.

Value is invalid JSON

📌 Cause: When it comes to metafields, the value you are entering does not match the format expected by Shopify.

✅ Solution: The easiest way to understand the correct format is to do the reverse:

1. Add a value directly in Shopify.
2. Save it.
3. Check how that value appears in your synced Airtable base.

This shows you the format Shopify expects, so you can replicate it when editing from Airtable.

AMBIGUOUS_FIELD_NAMES

📌 Cause: You are trying to create a field with a name that already exists — either a synced or unsynced column.

✅ Solution: Choose a different name for your column.

Other errors

Multiple / mixed errors

📌 Cause: Several different errors are appearing across records and operations, not tied to a single field or action.

✅ Solution: Check the related fields and if your workflow is correct. Many of these can be resolved with a few quick adjustments to your data or workflow. If you're struggling to put in place an automation, our in-house Airtable Experts can help you in a Studio mission. Simply reach out to us and we'll tell you how that works!

👉 What to do if my synchronization is not working

Updated on: 19/06/2026