Skip to main content

1001W: Key data is missing

What does this mean?​

Your message includes one or more IDs that do not exist in SyncHive.

Example:

{
  "meta": {
    "shape": "Product",
    "integrationKey": "shopify_integration"
  },
  "data": {
    "hiveId": "66EA94323C36",
    "name": "Toaster",
    "productCategory": [
      {
        "externalId": ["7d0444e2-d63f-4422-828f-3521083c5ec1"] <-- This ID does not exist in SyncHive
      }
    ]
  }
}

In this example, the externalId provided for productCategory refers to a record that doesn’t exist in SyncHive.

How does SyncHive handle it?​

SyncHive will continue to retry saving this message. Unless the records for the missing ID(s) are created in SyncHive, the message will eventually become a stuck message.

When does this happen and what can I do about it?​

This happens when your ID resolution configuration is set to “Retry if Not Found.” This is the expected behavior.

If this is not the desired outcome, review and adjust your ID resolution settings in the SyncHive Connect app.