I am trying to enable smart search on a particular record type, but I keep getting "Indexing failed" errors. I'm new to this feature, so I'm not really sure where a good place to start troubleshooting is, but I've listed what I've done/noticed below and attached a screenshot of the error.
If anyone has some other ideas of what might be causing this, what I can try, or could point me to the log where I could get some more details, that would be greatly appreciated!
Thanks,
Jack
Discussion posts and replies are publicly visible
Jack Ferguson said:When performing a full sync on the record, the "total record type rows" shows that it has 2 more rows than the "total source rows", but when viewing the record list the row count is correct.
This sounds suspicious. But, I suggest to open a support case and report this behaviour.
Failed records likely have invalid/missing primary keys or data that can't be indexed. Check if those specific Ids exist in your source and ensure your source query filters match your sync filters.
Hey Jack, that's a tricky one! The different primary key type definitely seems like a potential culprit. The discrepancy in row counts is also pretty sus. Have you tried looking at the sync logs (usually in the admin console) for more details about those extra rows? I know it's a long shot, but I once saw a weird issue caused by unexpected characters in the data messing with the indexing process, almost like the data was trying to do some dreadhead parkour through the system and tripping everything up! Hope you find the solution!
Shubham,
Could you elaborate on what kind of data can't be indexed?
The record syncs fine and there are no sync filters, which would indicate that there are no missing/invalid primary keys, just keys or data that can't be indexed.
aidang181818 said:Have you tried looking at the sync logs (usually in the admin console)
I'm not aware of any logs that live in the admin console. Could you tell me the name of this log and where I might find it?
aidang181818 said:issue caused by unexpected characters in the data
What kind of characters caused this issue? The primary keys listed in the error message all had "-" in them, but there are more than 410 primary keys with that symbol in the record, and I can't see the rest of the failed primary keys to confirm if that pattern holds.
Check if the failing records have nulls or unusual data in your smart search fields.