My SuiteCRM instance stopped because the disk got full. When investigated, I had dev/vda1 was 100% full. Further, the highest usage was coming from
/var/lib/mysql/suitecrm (Suitecrm Database)
The AOW processed tracks Workflows that have “Repeated Runs” unchecked, so they need to track which records it was run on, to prevent from running again on the same record.
so you have to be careful when deleting rows form there. It’s likely that millions of rows can be deleted safely, BUT only you can know the meaning of your Workflows and whether it is a bad thing that they will be run again for some record.
So review the logic of your Workflows and then try to clean up stuff related to deleted records, for example, or cases where the “No Repeated runs” condition wasn’t really necessary.
That’s weird, if you don’t have workflows defined…
If I were you I would try to understand better why that data is getting added to the table. For this, it would help to have some notion of that data, before you delete it… dates, which records it references, etc.
Okay update: looks like we did setup some baby ones last fall but forgot about them – not even sure what they are doing for us atm other than taking up a lot of diskspace
If your workflows allow “repeated runs”, they don’t have those aow_processed space problems.
If they are not running on “all records”, they also generate less rows there.
Finally, this is all a function of the number of records on the module table (the module on which the Workflow runs), so maybe a clean-up there is in order.