Skip to main content

Message contains references to record(s) that do not exist

What does this mean?

The document that SyncHive was trying to process contains references to other documents that do not exist in SyncHive.

For example, a Product document contains a reference to a ProductCategory that does not exist in SyncHive:

{
"@type": "Product",
"name": "T-Shirt",
"sku": "448114",
"description": "Classic Organic T-Shirt.",
"externalIdentity": [
{
"@type": "ExternalID",
"internalType": "Product",
"externalSystemCode": "Shopify",
"externalId": "2364423996"
}
],
"productCategory": [
{
"@type": "DataReference",
"schemaName": "SyncHive",
"shapeName": "ProductCategory",
"externalIdentities": [
{
"integrationKey": "Shopify",
"externalId": "5252286154" <-- This ProductCategory does not exist in SyncHive
}
]
}
]
}

How does SyncHive handle it?

SyncHive will continue to retry saving this record. Unless the above record has been created in SyncHive, this will continue to fail.

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

There are a number of possible causes and ways to resolve this issue.

  • The document that SyncHive is trying to process should have been filtered by an Integration filter:
    • Check the record in the source system to determine whether it should have been filtered.
  • The referenced document(s) have been filtered out when they should not have been:
    • Check your filter configuration for the referenced document(s) in SyncHive.
  • Documents are waiting to be processed by SyncHive:
    • If referenced document(s) arrive later in SyncHive, this issue will resolve itself.
    • If referenced document(s) never arrive in SyncHive, the original document will be eventually dead-lettered and will not be saved in to SyncHive. Reference document(s) that never arrive in SyncHive are often the result of deleted or bad references. Check that the record in the source system is valid.
  • A Connector bug has produced bad references in the document:
    • Check the latest version of the Connector. You may need to update or roll-back the version number.
  • A Connector configuration issue has produced bad references in the document:
    • Check your Connector configuration in SyncHive for issues.