Order Sync History

as shown in the order view screen, a history of sync actions performed for this order is retained history items are saved to the klevu sync order history database table and contain the following information date and time the action was performed what action was taken (for example, queueing for sync; starting processing) the initiator of the action (for example, the order save event; cli command) whether the action completed successfully a json encoded string of additional information this information varies based upon the action performed; initiator; etc, but generally will contain the following details the magento order id the magento store id sync status before the action was performed sync status after the action completed pruning history records by default, all history records are retained indefinitely for stores with high order volume, this may introduce performance and storage concerns and the number of records builds up as such, the module can be configured to prune old records automatically to enable order history pruning, enter values in one or both of the following configuration settings klevu > developer settings > order analytics > remove history for successfully synced orders after (days) klevu > developer settings > order analytics > remove history for failed synced orders after (days) these values will determine the number of days for which to hold onto sync history for orders in the following statuses respectively “complete”, “error” orders which are still pending synchronisation (including those which have been requeued) will not have history records removed note, this setting is global, meaning you cannot configure different thresholds based upon store sync history is pruned based upon the timestamp of the history item, not the order date, meaning orders where processing spans multiple days may show partial history sync history pruning is performed by the klevu analytics remove synced order history cron job, which is scheduled to run at midnight each day