AutomateWoo

Allow deletion/auto-cleaning of historic workflow logs while still keeping rules/filters based on “workflow count” intact without moving stored log data to order meta (which would only shift the storage overhead elsewhere rather than fully addressing/optimising the database).

Currently, when any of the logs are deleted, workflows that rely on those logs for the “workflow count” rules to work would consider the next workflow run after deleting the logs (even when using the new auto-cleanup setting) to be the first run for the customer/order/etc. Many workflows would have the “workflow – run count for order = 0” rule set up as a safeguard to avoid it from running multiple times for the same order. This stops working when the logs are cleaned. The same goes for manual workflows that are frequently used to adjust historic orders/order meta and can easily create logs with thousands of entries yet they can’t be deleted because if admins want to rerun the manual workflow for any orders that hadn’t been adjusted by the workflow previously the “workflow run count” rules need *all* historic logs for the flow.

[This feature request originated from Woo support ticket #11441442 — the Happiness Engineer confirmed the request has also been passed along internally.]