I have been running an install of SuiteCRM for over 2 years now. Tons of custom work has been put into it. Custom modules, workflows, logic hooks, custom actions, third party api integrations and the list goes on. Pretty much the whole system has been customized to fit out needs. To say the least it has adapted very well. Within in the last week I have had the strangest problem and I will attempt to describe it below. I If anybody has experienced this before please chime in.
On a particular set of records whose relationship I can not determine, every workflow and logic hook gets run for no apparent reason. Every single one fires regardless of if the conditions of the workflow are met.
Please help as this is causing major issues with keeping our data accurate.
Tell us your current SuiteCRM version and check if you’re getting this bug in 7.10.4:
https://github.com/salesagility/SuiteCRM/issues/5803
Ouch… that’s really old.
Can you please try running the query on the top of this post?
https://pgorod.github.io/Database-tables-size/
I would like to check if you have any overgrown tables in your system, specifically the job_queue and aow_processed tables which might be messing up your Workflows.
Also check your logs for any FATAL or ERROR messages:
- suitecrm.log
- php_errors.log
CONCAT(table_schema, '.', table_name) | rows | DATA | idx | total_size | idxfrac |
+------------------------------------------+--------+--------+--------+------------+---------+
| admin_crm.emails_text | 0.094M | 0.946G | 0.006G | 0.951G | 0.006 |
| dev_crm.emails_text | 0.092M | 0.933G | 0.006G | 0.939G | 0.006 |
| admin_crm.job_queue | 0.032M | 0.388G | 0.003G | 0.392G | 0.009 |
| dev_crm.job_queue | 0.029M | 0.365G | 0.002G | 0.367G | 0.007 |
| admin_crm.aow_processed_aow_actions | 0.496M | 0.063G | 0.108G | 0.171G | 1.724 |
| admin_crm.aow_processed | 0.484M | 0.073G | 0.088G | 0.161G | 1.212 |
| dev_crm.aow_processed_aow_actions | 0.476M | 0.060G | 0.083G | 0.143G | 1.372 |
| admin_crm.opportunities_audit | 0.134M | 0.130G | 0.010G | 0.140G | 0.075 |
| dev_crm.opportunities_audit | 0.133M | 0.130G | 0.009G | 0.139G | 0.069 |
| dev_crm.aow_processed | 0.464M | 0.070G | 0.056G | 0.126G | 0.800 |
| admin_crm.email_addr_bean_rel | 0.406M | 0.053G | 0.042G | 0.094G | 0.788 |
| dev_crm.email_addr_bean_rel | 0.388M | 0.050G | 0.031G | 0.081G | 0.613 |
| admin_crm.emails_email_addr_rel | 0.184M | 0.021G | 0.021G | 0.042G | 1.023 |
| dev_crm.emails_email_addr_rel | 0.181M | 0.021G | 0.017G | 0.038G | 0.832 |
| admin_crm_original.emails_email_addr_rel | 0.162M | 0.018G | 0.018G | 0.036G | 0.952 |
| admin_crm.emails | 0.099M | 0.018G | 0.012G | 0.030G | 0.649 |
| dev_crm.emails | 0.098M | 0.018G | 0.011G | 0.029G | 0.596 |
| admin_crm_original.emails | 0.087M | 0.016G | 0.010G | 0.026G | 0.662 |
| admin_crm.emails_beans | 0.076M | 0.010G | 0.016G | 0.025G | 1.586 |
| dev_crm.emails_beans | 0.075M | 0.010G | 0.012G | 0.021G | 1.229 |
It’s old but what has been changed that would make my life that much better? I have a dev version I have upgraded and I am in the process of making sure all the customizations work, but I have not seen a super compelling reason to force the organization to change yet. Please enlightenon the best improvements.
The biggest reason is that you’re running a super-insecure app on the internet. There have been hundreds of security fixes, both to PHP and to SuiteCRM itself.
The new versions of SuiteCRM are compatible with PHP 7.0 which brings you much added speed and security.
Then there are countless bug fixes and some new features.
I would advise an upgrade at least to the latest 7.8.x which is stable and uses the same email module you’re used to.
About your database, I believe you really need to clean up you aow_processed and aow_processed_actions tables. They have grown so big that probably some of your queries are failing and that explains your Workflows malfunctions. However, if this is the case you should be seeing errors inyou logs, and you should really check your logs before anything else.
Is your Scheduler Job “Prune database on the 1st of month” running successfully lately?