You need to sign in to do that
Don't have an account?
Andres Schmois
Salesforce Bug on System.schedule
I've been coding in a sandbox and figuring out how to schedule jobs through Apex and I ran into a few errors where I was receiving an error "Based on configured schedule, the given trigger will never fire". Anyways after a bit of changing code around and finding out why I was getting that, I went into my scheduled jobs and now I have a couple orphaned AsyncApexJobs that I cannot delete because they do not belong to a parent cron trigger. I've seen a few of these errors on the forums and all answers say that Salesforce backend team had to delete the jobs themselves.
If you want to reproduce this error: Call System.schedule with a cron trigger in the past, and you will get a stuck job.
I need some help from someone in the Salesforce team to delete the orphaned AsyncApexJobs.
Related: https://developer.salesforce.com/forums/?id=906F0000000BOuqIAG
Related 2: http://avionsalesforce.blogspot.com/2016/03/how-to-terminate-asyncapexjob-exception.html
If you want to reproduce this error: Call System.schedule with a cron trigger in the past, and you will get a stuck job.
I need some help from someone in the Salesforce team to delete the orphaned AsyncApexJobs.
Related: https://developer.salesforce.com/forums/?id=906F0000000BOuqIAG
Related 2: http://avionsalesforce.blogspot.com/2016/03/how-to-terminate-asyncapexjob-exception.html
Try this and see if it works:
All Answers
Try this and see if it works:
It's a shame a salesforce bug has to be fixed by a third-party tool and treat their users like I was treated for a bug on their platform. Guess that's what they call the Salesforce Way™
Thank you for your time anyways.