• State Suggested Answer
  • Replies 5 replies
  • Answers 2 answers
  • Subscribers 13 subscribers
  • Views 102 views
  • Users 0 members are here
Related Discussions
Home » Discussions » Data and Records

Indexing Fails When Configuring Smart Search

Jack Ferguson
Certified Senior Developer

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.

  • I have successfully set up smart search on 2 other record types in the same environment
  • A difference between the 2 records successfully using smart search and the one that is failing, is the primary key of the failing record is type text and can contain some symbols (periods and hyphens mostly) while the other 2 are type integer. Not sure if that's relevant or not.
  • 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.
  • I've tried changing the fields that smart search uses with no effect

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

Parents
  • 0

    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!

Reply
  • 0

    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!

Children
  • 0
    Certified Senior Developer
     in reply to aidang181818
    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.

© 2025 Appian. All rights reserved.
We want to hear from you! Submit a review on Gartner or G2.