SugarChimp

Thanks for reaching out. I'd like a few more pieces of diagnostics to see if we can narrow down what the issue could be. Can you walk through the steps below:

1. Right click on your browser and select Inspect. Switch to the Console tab, and then paste: SUGAR.App.api.call('get',SUGAR.App.api.buildURL('SugarChimp/setting/logger/debug'),{},{});
2. Navigate to a contact and make a change. Save the record as you normally would.
3. From within Sugar Admin, click System Settings.
4. Scroll to the bottom of the page and click View Logs. Then click All.
5. Copy/paste what appears into a .txt file and send it along to us at mailchimp@fanaticallabs.com.
6. When completed, you can return the logger level to normal by pasting the following into the Console tab: SUGAR.App.api.call('get',SUGAR.App.api.buildURL('SugarChimp/setting/logger/normal'),{},{});

Thanks for your help in troubleshooting.

Best, Heidi

You can send it to us at mailchimp@fanaticallabs.com.

Thanks! Heidi

Just wanted to follow up on this specific case. As mentioned through our email exchange, it sounds like this may not be related to SugarChimp as SugarCRM was able to replicate when SugarChimp logic hooks were removed. I'm going to close this case for now, but if the results of their test indicate an issue with SugarChimp, please let me know and we'll be happy to troubleshoot further.

Best, Heidi

Sugar Support cloned the career vision instance and disabled the Sugar Chimp and Ball API schedulers, and the search index problem was not reproduced. So the thought is now that schedulers may be interfering with the indexing.

Just wanted to quickly update this ticket with the information we chatted about through email and during our call:

We determined that once you've done your newsletter for this month, you'll make the schedulers related to SugarChimp inactive to see if the issue continues. As a reminder the steps for doing that are below:

1. From within the SugarChimp Health Status page, click view scheduler
2. Click Edit at the top left page
3. Use the drop-down on the right that says Active and select Inactive
4. Click Save

Once inactive, please be sure to check in with your team to see if the issue continues. I'm inclined to think it's related to the BallAPI scheduler failing every minute, so you'll also follow up on that issue with your Sugar administrator.

I just wanted to check in to see how SugarChimp was working. If you need anything further, please let me know.

Best, Heidi