Sync

attribute sync is responsible for sending attribute data to klevu the type of api request depends on the next action column in the klevu indexing attribute database table if that column is set to add then an add request will be sent, if it is empty no request will be sent the population of klevu indexing attribute database table is controlled by attribute discovery and update attribute sync does not determine the action to be performed attribute sync is triggered via cron via cli \klevu\indexing\service\attributesyncorchestratorservice responsible for attribute sync all the above methods of triggering attribute sync use this service cron as with all cron tasks added by version 4 x of the klevu integration, attribute 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 attributes sync runs every 10 minutes by default this can be configured in the magento admin, stores > configuration > klevu > data sync > indexing > attribute indexing sync frequency the default setting can be found here module m2 indexing/etc/config xml the configuration for the cron can be found here module m2 indexing/etc/crontab xml module m2 indexing/etc/crontab xml \<job name="klevu indexing sync attributes" instance="klevu\indexing\cron\syncattributes" method="execute"> \<config path>klevu/indexing/attribute cron expr\</config path> \</job> cli klevu\ indexing\ attribute sync the sync can also be triggered via cli and has 2 optional parameters api keys \[optional] comma separated list of api keys to sync attribute types \[optional] comma separated list of attribute types to sync, options klevu product klevu category increasing the verbosity of the command will give you more information using v , vv , or vvv e g bin/magento klevu\ indexing\ attribute sync \\ \ attribute types="klevu product" \\ \ api keys="klevu example js api key" \\ vvv if an attribute has been registered with klevu for indexing that does not mean it is automatically sent to klevu it means it can be sent to klevu entity data indexed to klevu is defined in the indexing pipelines yaml files for custom attributes, you can either enable autogeneration of the yaml files in the admin at stores > configuration > klevu > developer settings > pipelines > enable autogeneration of configuration overrides and select the product types to send this data for in automatically generate pipeline configuration for section of the attribute properties add your own yaml file for the attribute see pipelines customisation