Salesforce Stack Exchange is a question and answer site for Salesforce administrators, implementation experts, developers and anybody in-between. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am running a batch job but it gets stuck in middle and not moving further. Has anyone faced similar thing before?

share|improve this question
Ya this is very common issue .Batch Jobs runs in async mode and only available when we get free resources at sfdc end . – Mohith Shrivastava Dec 7 '12 at 6:02
But it stuck for half an hour and not moving. Will it get resume automatically? – doga Dec 7 '12 at 6:09
It will .I had same issue and it resumed automatically.Hope same here – Mohith Shrivastava Dec 7 '12 at 6:50
Doga is it still stuck? – Andrew Fawcett Dec 7 '12 at 9:04
Turn debug logs on for the user the batch is running as and check if there is any movement in the logs. Also I'm guessing by stuck you mean Batches processed count isn't incrementing. Any fatal errors showing in Monitoring > Apex Jobs – techtrekker Dec 7 '12 at 9:20
up vote 2 down vote accepted

Batches can be stuck and give no indication of a failure if there is a fault with the data that salesforce has not handled. For example, this can happen with objects like opportunity and opportunity line item, for sandbox refreshed from production during high user activity period. It might be worth raising a case with salesforce if this is happening quite often so that they can look into their logs and come back to you with details. This process would take a couple of days

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.