Skip to main content
Topics#IntegrationSara Landis's Question
Sara Landis asked in #Integration
Feb 2, 2017, 8:04 PM

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?
18 answers
  1. InjureFree Support
    Mar 20, 2017, 7:10 PM
    For those looking for the solution to Sara's issue (not the other issue introduced later in the thread), here's a way to get this fixed.  If you don't have Developer Support due to subscription level, your first battle will be to convince the Email & Desktop Integrations team that this is a known SF issue and needs to be handled by Dev Support anyway.  They will attempt to close the case and refer you to this forum.

    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.

     
Write an answer...
0/9000