Feed Indexer Failure (View Specific)

Problem

Bloomreach product feeds can be tracked using Bloomreach Dashboard. Feed processing is divided into two steps:

  • Feed processor step
  • Feed indexer step
    You might sometimes receive feed indexer is failing with the below error:

📘

Error Message

The indexing step of a full feed failed because the count of valid products is below the allowed threshold.

Reason

There are various reasons for this error. Open a Support Ticket if you are unable to debug and solve the issue using the below steps.

Debugging Steps

Compare the statistics of the latest feed run with the last successful feed run from Bloomreach Dashboard. For example:

Feed Indexer Runnum

Last Successful Runnum:

Feed Processor succeeded. Feed Indexer failed.

Feed Processor succeeded. Feed Indexer succeeded.

Statistics
Unique Pids: 170089
Unique Skus: 0
Unique Urls: 170089
Indexer statistics
Valid products: 170089
Solr docs indexed: 170089

Statistics
Unique Pids: 170010
Unique Skus: 0
Unique Urls: 170010
Indexer statistics
Valid products: 1038441
Solr docs indexed: 1038441

Alternatively, the feed indexer status can be checked in Catalog Management:

16001600

If the feed has view data

  • Bloomreach validation check on count:
    • The indexer is failing in PROD due to a safety threshold.
    • In addition to the product id count, Bloomreach also has a validation check on the number of documents a feed generates.
  • Reason for count drop in indexer: There could be multiple reasons for count drop in indexer. Some of the scenarios are described below:
    • If the latest full-feed has drastic decreases in the number of indexed products.
    • If the latest full feed has different views/stores to account for different pricing, names, banners, and markets.
      • Each view override is a document.
      • Product id creates multiple documents due to this view/store information.
      • Example Feed with views: If full-feed is a JSON file:
{
   "op": "add",
   "path": "/products/435898",
   "value": {
     "attributes": {
       "title": "Three-Pocket Straight Leg Jeans",},
     "variants": {
       "43589802": {
         "attributes": {
           "description": "For the most….",}}},
     "views": {
       "A": {
         "attributes": {
           "currency": "AED"}},
       "B": {
         "variants": {
           "43589801": {
             "attributes": {
               "availability": true,}}}},
       "C": {}
       //No overrides     }}}

Three documents are created for:
- View A
- View B
- Product

491491

Example Feed with views: If full-feed is a XML file:

<Product>
   <pid>AAACLBUDGET</pid>
   <title>Anchor Audio ACL-BUDGET Acclaim Budget Wireless Package</title>
   <variants>
     <variant>
       <skuid>AAACLBUDGET</skuid>
       <view_id>A</view_id>
       <Availability>True</Availability>
     </variant>
   </variants>
 </Product>

Two documents are created for:
- View A
- Product

370370

If the number of documents has been drastically decreased, it causes a drop in count of valid products.

  • The error may appear when Merchant has multiple views and there is no view information for a view specific attributes in feed data.
<view_specific_attribute><[]><view_specific_attribute>

Example: if a feed does not has view data:
Only one documents is created since there is no view information:
- View A
- Product

207207
  - If there is no view data, Bloomreach cannot create views for that field 
    - Each view override is a document. Since view-overrides are not created, it causes a drop in count of valid products. 
  • Indexer Failure
    • The indexing step of a full feed fails because the count of valid products is below the allowed threshold.
      • Count dropped from 1,038,441 to 170,077 in the example above.

Solution

  • Feed changes are required to fix the issue: Make changes in feed, and send quantity for each view to Bloomreach Support.
  • There should be region wise quantity for View specific attributes in the Feed. Example: If full-feed is a XML based file:
view information passed
<view_specific_attribute>US title|EU title|APAC title</view_specific_attribute>
No view information passed
<view_specific_attribute></view_specific_attribute>

Did this page help you?