We got some performance issues with that task. Our MySQL replication needs 1-2 hours to catch up the master.
@user121216 thanks for the PR. would you mind resolving the conflicts?
@user121216 cheers for the suggestion, really appreciated. In the last release / config we've already added a feature to do this:
Just set it to a really high value and it won't be executed.
Let me know if this doesn't work for you.
Sorry, my fault. I thought, I forked the latest version, but I've already had forked years ago.
I will try
delete_logs_unused_actions_schedule_lowest_interval. Thanks for the hint!