Support

February 13, 2024 at 3:57 pm

So it sounds like it already is automated, you made the change to the retention settings yesterday, right? So it will have run 2-4 times so far removing 8k rows.

We keep the limit relatively low to prevent timeouts on various hosting types, what type of hosting are you using? The cron removes 2k rows each time it’s processed so for your ~100k and assuming 80% of those are ‘old’ messages that’s roughly 20 days to delete those 80k messages.

How long did it take to process the request when you clicked run now above?

If it was quick you could set the limit higher and manually run that cron a few times, that’s the ‘safest’ and likely quickest option:

add_filter('EEM_Message__delete_old_messages__limit', 'tw_ee_increase_delete_old_messages__limit', 10);
function tw_ee_increase_delete_old_messages__limit($limit) {
    return 5000;
}

Add something like the above to increase the limit to 5000, you may get away with higher values depending on your server. It depends how long it took to process the above request, if it was pretty much instant you have a lot of wiggle room and can go higher. At that value your looking at 8days if you leave it as is, or just manually run the cron like you did above until your happy with the number of messages (16 times would clear 80k).

Once you have the message count down the cron job should then keep on top of your messages as new ones are created so this is just to get your current backlog cleared.