Skip to main content

1002E: 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 stops processing the message and sets it aside.

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

This can happen in two cases:

  • Your ID resolution configuration is set to “Fail if Not Found”
  • Your ID resolution configuration is set to “Retry if Not Found”, and the message has retried too many times and become stuck

Both of these outcomes are expected behavior based on your ID resolution settings.

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