Cron triggers can sometimes fail/misfire and cause Apex jobs to get stuck in Queued status
Last updated 2016-07-28 ·Reference W-2400662 ·Reported By 4 users
"The issue of job status not being updated due results from a lag between the Apex code that is being executed and the moment when the Cron expression is interpreted to generate the time of the next job run.
1) Run Batch Apex job which fails
2) This will progress until failure
3) Job will stay in queued status with no error logged in UI
At this time the only workaround is to manually handle the Apex job
Is it Fixed?
Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.