FAQs and Troubleshooting

i can’t see synced data in the log files by default, all logs are set to “standard” monolog\logger info to see indexing data in the logs set the indexing logger to “verbose” monolog\logger debug that setting can be found here stores > configuration > klevu > developer settings > logging i have integrated my store, but no entity data has been indexed to klevu attribute discovery and attribute sync are triggered on integration as is entity discovery entity sync however is handled via cron please ensure you have corn running correctly the indexing cron default schedule is set to every 30 minutes this can be customised in the admin stores > configuration > klevu > data sync > indexing as with all cron tasks added by version 4 x of the klevu integration, order sync cron tasks use the dedicated klevu cron group, allowing granular configuration of scheduling and run options we recommend using the native magento cron to run these jobs, configuring schedules if necessary, rather than a custom server side cron implementation of the cli command how do i exclude certain products/categories/cms pages from the index? by default, klevu will index all enabled products/categories/cms pages there are admin settings to exclude disabled products/categories/cms pages or out of stock products if you wish to exclude entities from the sync based on any other attribute you can add an is indexable condition to the determiner via etc/di xml how do i exclude products from indexing by visibility? by default, we do not filter products by visibility when indexing data we have an optional module that can be installed to add the ability to filter products on visibility before indexing we have 2 future releases planned integrate your auth keys at website scope (same auth keys for multiple stores) indexing visibility for customer groups this module would cause issues with either setup as products could have differing visibility between stores and customer groups, potentially triggering a delete request when the product should be sent to klevu the module can be installed via composer or found on github composer require "klevu/module m2 indexing products exclude by visibility" the frontend modules filter search requests based on visibility which matches the default magento behaviour category search or search for search requests category search or category for category navigation requests how do i sync all products/categories/cms pages? the klevu modules always send a delta sync, i e just the products that need to be updated which products to send to klevu is determined by the next action column in the klevu indexing entities we have a cli command to set entities to require an update (or addition/deletion if applicable) in that command instead of passing a list of ids to update we can pass entity ids="all" this will set all entities, that are indexable, to require an update these entities will be synced to klevu on the next cron run or the sync can be triggered via the sync cli command https //docs klevu com/klevu magento v4/entities sync#7d59x why are configurable and variant products indexed as out of stock when they are in stock? in magento 2 4 4 2 4 6 p7 , there is a bug in magento msi where a configurable product became out of stock it would not come back into stock, even if the admin displayed stock status in stock this issue was fixed in the 2 4 7 release and can be applied via quality patch id acsd 56546 if that does not fix the issue, please review the 2 4 7 release as there were multiple inventory issues fixed in that release how stock info indexed for products and variants?