Save Your Team Countless Hours. SugarChimp syncs your lists in both directions so you can work in your preferred app. Segment and group your Mailchimp subscribers based on Sugar data so you can market to the right people at the right time. Compatible with all versions and editions of Sugar and SuiteCRM. Created by Fanatical Labs, 2023 SugarCRM Partner Award Winner.
#1602 - Target List not sending subscribers from SugarCRM to Mailchimp List
I just installed SugarChimp basic onto our SugarCRM Professional v6.5.16 (hosted by a 3rd party Cloud LAMP server)
My Sugar scheduler job is running, although for SugarChimp job the "Last Successful Run" field is Never.
I configured one of my Sugar Target lists to sync over to a list in my Mailchimp account.. The step to sync these went ok yesterday, but none of the records in my Sugar Target list are going over as Mailchimp subscribers in my Mailchimp list.
When I click on SugarChimps Health Status link from Sugar's Admin Panel, everything looks ok EXCEPT 'Last Ran' has a red checkmark and says "has not run yet'
Thanks Jennifer C
-
"The new version does this much better and is actually much more feature rich than the old version 3 plugin. https://www.infosectrain.com/" - Infosec Train
Read More Reviews
- Most Recent Love from Users
melissa- Westcoat
- Mark Westerhoff
- danielolivas
- kgm
- Evolution Marketing
9 years ago
Hi Jennifer, sorry for the issues.
If you go to Sugar > Admin > Scheduler page, and click on any of Schedulers with an interval of "As often as possible", does it show any of those schedulers have run recently? If not, there may be something going on with your Cron job.
Please send the following to support@sugarchimp.com so we can take a closer look:
1) Send us a screenshot of the Health Status page (Sugar > Admin > SugarChimp Health Status) 2) Send us a copy of the sugarcrm log file
Thanks!
9 years ago
We were able to resolve this over email. The cron job was using PHP 5.2 where SugarChimp requires PHP 5.3. Once PHP was upgraded, everything started working as expected. Closing this case out now. Thanks!