The v2 Job Reports section of the Algolia BM module shows the results of each job’s last three runs.
It summarizes the data in the log files that each job generates.
Access this data from Administration > Operations > Jobs > [Job Name] > Schedule and HistoryThe tables for each job contain the following columns:
Field title
Description
start
Start date and time of the job.
end
End date and time of the job.
products to be sent / total
Number of products (or categories) to send for each locale, and the total number of items processed. Due to product filtering, these numbers rarely match. For example, the job doesn’t send product masters by default. For the delta jobs (AlgoliaProductDeltaIndex_v2, AlgoliaProductPriceDeltaIndex_v2, and AlgoliaProductInventoryDeltaIndex_v2), the total is the number of records read from the B2C delta export XML files.
# locales
Number of locales configured for the site. With more than one locale, each product to send results in one record per locale.
records to be sent
Number of records to send to Algolia. This is usually the number of products to send, multiplied by the number of locales.
records sent / failed
Number of records sent to Algolia, and the number of records that failed to send. If the failed count is above zero, red marks the value.
chunks sent / failed
Number of chunks sent to Algolia, and the number of chunks that failed to send. If the failed count is above zero, red marks the value.
error
If an error occurs during the job, the error message appears here in red. Otherwise, this field stays empty.
If you set the cartridge to index with the Ingestion API, the records sent and chunks sent counters reflect transport-level acceptance only.
This applies to these product job reports: AlgoliaProductIndex_v2, AlgoliaProductDeltaIndex_v2, AlgoliaProductPriceDeltaIndex_v2, AlgoliaProductInventoryDeltaIndex_v2, AlgoliaProductPriceIndex_v2, and AlgoliaProductInventoryIndex_v2.
Indexing is asynchronous, so it happens later.
Record-level errors (for example, “record too big” or failed transformations) show up later in the Algolia dashboard’s Connector Debugger, not in this report.
Category and content job reports aren’t affected.
Algolia job reports use B2C Custom Objects for storage.
Algolia creates a custom object of type AlgoliaJobReport for each job run.
Algolia deletes these custom objects automatically after 30 days.
