Apex Code Development You need to sign in to do that
Don't have an account?
Sara Landis MailChimp batch apex jobs stuck in holding
I have spent the last week working with Mailchimp to troubleshoot the MailChimp for Salesforce plugin, which is no loner syncing contacts from Salesforce onto our MailChimp list. MailChimp tech support has requested information from Salesforce Support in order to proceed with the troubleshooting. As a standard customer, I have been told the only way to access any support is through this forum, so I am hoping someone has insight!
What we know:
• Users of the MailChimp for Salesforce integration are experiencing an error that “a batch job is already in process”.
• From what we can see, these batch jobs are in a ‘holding’ state in the Apex flex queue, and are never moved to the Apex job queue for processing.
• In order to protect org resources, MailChimp integration will not start a second batch job if a MC4SF batch is already in the apex queue.
• We have established that there are no other apex jobs currently running that would cause the hold in the flex queue.
• Since we can verify that these batch jobs are being created successfully, the issue appears to be with how they are being handled for processing in these queues, which is a function controlled exclusively by Salesforce.
MailChimp support has asked me to find out:
• What could cause a job to remain in a ‘holding’ state in the flex queue?
• Is there anything that would prevent a batch job from being able to move from the flex queue to the job queue?
• Is there anything unique to this specific org or the Apex flex queue that would prevent these jobs from running as expected?
What we know:
• Users of the MailChimp for Salesforce integration are experiencing an error that “a batch job is already in process”.
• From what we can see, these batch jobs are in a ‘holding’ state in the Apex flex queue, and are never moved to the Apex job queue for processing.
• In order to protect org resources, MailChimp integration will not start a second batch job if a MC4SF batch is already in the apex queue.
• We have established that there are no other apex jobs currently running that would cause the hold in the flex queue.
• Since we can verify that these batch jobs are being created successfully, the issue appears to be with how they are being handled for processing in these queues, which is a function controlled exclusively by Salesforce.
MailChimp support has asked me to find out:
• What could cause a job to remain in a ‘holding’ state in the flex queue?
• Is there anything that would prevent a batch job from being able to move from the flex queue to the job queue?
• Is there anything unique to this specific org or the Apex flex queue that would prevent these jobs from running as expected?
Once it's at Dev Support, you'll need to get this escalated to Tier 3 Dev Support, this isn't so much a challenge as it is time-consuming. Once it gets there, you should get it resolved. I recommend getting on the phone with a supervisor as soon as you submit your case, explain the situation and appeal to their common sense to have a Tier 3 Support tech go straight to the fix instead of walking through all the normal troubleshooting steps at all Tiers, which will prove pointless.
Refer to this forum post (https://developer.salesforce.com/forums/ForumsMain?id=9060G000000I4EzQAK) and include the following, or something similar, in your case description to supplement your other info:
Please review Case 15876990 which details the same problem I'm having, but with another customer. SF Tier 3 Developer Support can easily fix this when they look for and remove any Apex Token jobs stuck in queue, caused by a SalesForce platform bug. One SF tech that has fixed this is Varun Guruvugari, Success Agent - Tier 3.
This is NOT a developer issue. It is a functionality/operational issue. I'm not asking for support to build anything. The fix is only under your control. I understand why you restrict Developer Support to certain subscription levels. However, when it's the platform that should run the job and isn't doing it, as is the case with this issue, that must be something that should be looked at for any customer that has the capability to run jobs, regardless of subscription level.
The job stopped being run and since we don't develop anything, the package being run hasn't changed (its managed). This is something for Salesforce to fix.
All Answers
Sara, I don't have batch jobs like yours, I don't think - but the time stamp of the errors matches about 1/2 hour past when a couple of our MailChimp member queries were trying to sync to Salesforce?
Norm, our subscribers all seem okay, and the errors seems to have been generated during some kind of hiccup on the MailChimp side when the queries I mentioned to Sara just above tried to run. They are actually set for midnight, however, so I'm a bit stumped that all the errors (and the later "success" are time-stamped 12:27AM instead.
Not sure if any of this is helpful... perhaps the two of you know more than I, or someone else does, and will be able to enlighten the lot of us. :-)
Did you find the solutions for "Oops! It looks like the MailChimp API is unavailable for an unknown reason. Please check with MailChimp Support and try again later."
Same issue facing myself also. Please provide your suggestion.
Thanks,
@Leslie, sorry to not get back to you sooner. I don't yet have a solution to my issue. Mailchimp says that my two issues (people being removed from groups and the API error notification) are two sperate errors but I'm not convinced. If we add people back to groups, each night they are removed again around the same time that the API errors are generated. Will update when I have more info to share.
Would love to hear the solution once it's been resolved! Thanks for posting this!
Really annoying since the email is sent in my name, probably because I was the admin that configured the plugin. This morning 40+ of these emails were sent and received by a lot of the organizations Salesforce users...
Does anyone know how I can at least prevent this e-mail being sent to some of the users? Is there a setting somewhere where this can be configured? Not every user receiving these warning emails is an administrator.
I want to avoid deleting the entire app, which is tempting because the notification emails are so disruptive.
Connection User 02/20/2017 11:25:09 AM EST
Hi John,
Hope you doing great !
I investigated on this issue and was able to find that this is related to a known issue:
https://success.salesforce.com/issues_view?id=a1p3A0000008g2NQAQ
R&D team is presently working on this to get this bug fixed. This is expected to be resolved by summer'17 release.
You can just click on this issue "This issue affects me" and you would be notified about the updates on this issue.
Hence, I would go ahead and mark this case as "Bug Fix". You face any issues you can just a new case.
Thanks,
Ujjwal
"Mark Yohai
I was able to get SalesForce support to look at it after explaining it's an operational issue on their end, not a developer issue...then they resolved it as follows: We have identified the Issue and have deleted few Orphaned "ApexToken" jobs which were stuck in the queue because of a platform bug.
December 2, 2016"
I'm going to submit a new case to SF with this info. Will let you know how it goes.
Once it's at Dev Support, you'll need to get this escalated to Tier 3 Dev Support, this isn't so much a challenge as it is time-consuming. Once it gets there, you should get it resolved. I recommend getting on the phone with a supervisor as soon as you submit your case, explain the situation and appeal to their common sense to have a Tier 3 Support tech go straight to the fix instead of walking through all the normal troubleshooting steps at all Tiers, which will prove pointless.
Refer to this forum post (https://developer.salesforce.com/forums/ForumsMain?id=9060G000000I4EzQAK) and include the following, or something similar, in your case description to supplement your other info:
Please review Case 15876990 which details the same problem I'm having, but with another customer. SF Tier 3 Developer Support can easily fix this when they look for and remove any Apex Token jobs stuck in queue, caused by a SalesForce platform bug. One SF tech that has fixed this is Varun Guruvugari, Success Agent - Tier 3.
This is NOT a developer issue. It is a functionality/operational issue. I'm not asking for support to build anything. The fix is only under your control. I understand why you restrict Developer Support to certain subscription levels. However, when it's the platform that should run the job and isn't doing it, as is the case with this issue, that must be something that should be looked at for any customer that has the capability to run jobs, regardless of subscription level.
The job stopped being run and since we don't develop anything, the package being run hasn't changed (its managed). This is something for Salesforce to fix.
You can now easily integrate Salesforce and MailChimp together via MailChimp Salesforce Connector.
One which I would like to recommend is ChimpConnect (https://eshopsync.com/mailchimp/)
You can check out this to know more on how you can integrate MailChimp and Salesforce together.