Question2Replies95Views×Close popoverkeshav agarwal (keshava9) highmark highmark US View Profile keshava9 Member since 2013 6 posts highmark Posted: March 13, 2018Last activity: March 28, 2018Posted: 13 Mar 2018 0:04 EDTLast activity: 28 Mar 2018 14:27 EDT Closed Solved background merge hit exception:While running the Rules indexing we are seeing an error .background merge hit exception: _8e0:c204135->_8dq _8e1:c38220->_8dq _8e2:c52859->_8dq _8e3:c32539->_8dq _8e4:c3772->_8dq _8e5:c10277->_8dq into _8e6 [optimize] We have added a new knowledge content rule and that requires indexing to be done. Looks like because of this error that new rule is not getting indexed and thus not picked.Could someone please let us know what is this error and how to get rid of this.×Close popoverFacebookTwitterLinkedinEmail Copy Link Copied! Moderation Team has archived post This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question. Posted: 2 years agoPosted: 14 Mar 2018 16:17 EDT×Close popoverNick Loving (NickLoving_GCS) PEGA Senior Software Solutions Engineer Pegasystems Inc. US View ProfileNickLoving_GCS PEGA replied to keshava9That doesn't look like an error I've seen before. Can you provide the complete log file? Enabling debug on logger com.pega.pegarules.search.internal.es and reproducing the issue may also be helpful if you attach that log. If you'd rather not post the complete log here, an SR could be opened to look into this. Accepted Solution Posted: 2 years agoPosted: 28 Mar 2018 11:56 EDT×Close popoverkeshav agarwal (keshava9) highmark highmark US View Profilekeshava9 highmark replied to NickLoving_GCSThanks for the reply. We actually figured out the issue. The dynamic system setting for rule indexing was false and also the directory to write the index files was incorrect. Once we corrected that this error was never again.