Search Results

You actually do not need to even implement Schedulable to run a batch each hour. There is a method called system.scheduleBatch which will do the trick nicely here: public void finish(Database.Batchab …

You are trying to pass a Batchable implementation where Schedulable is expected. This is just one reason why it is better to roll both into the same class. Regardless, your schedule method should pass …

Once the schedule is already running, you execute the batch, not schedule it: public void execute(SchedulableContext context) { Database.executeBatch(new MyBatch()); } If you want a simple sche …

It's a multi-tenant system. Your server may be loaded up with requests at the time the job is scheduled to execute. You should read through these documents: The Force.com Multitenant Architecture As …

As you already know, time of execution is not guaranteed. That said, they will each start as close to the scheduled time as the system can manage.

You want the EndTime field on the CronTrigger object. You could see the end date for all scheduled jobs with this query: SELECT EndTime, CronJobDetailId, CronJobDetail.Name FROM CronTrigger WHERE Cro …

I recommend you use Data Loader for this task. Export the query you have already written Manipulate the CSV to set DisqualifiedReason__c and OwnerId to the proper values. Import the manipulated CSV …

Scheduling the job counts as pending work for the purpose if callouts. If you want to test the callout, manually run execute(null). To test the schedule itself, you'll likely find a @TestVisible flag …

I will pull my comments here into an answer. I suggest this general path: Create a Visualforce Email Template on Account. Have this template pull in relevant child Contact information. Create a c …

You have an extra opening curly bracket ({). That's forcing everything inside of it to be considered an initializer block and really confusing the poor compiler. global class MyClass { { …

You should absolutely move this logic into a batch. If you need to update all 22k records, you will run into governor limits. Note that it is not advisable to include child records via subquery in a q …

If the event was scheduled via the UI, you should be able to get the information you want via SOQL. Here's the problem: CronTrigger has most of the data points you need, which you can access through C …

When testing your scheduled jobs, asserting on the CRON string is going to far. You should just verify that the job got scheduled and leave it at that. MySchedulable job = new MySchedulable(); Test. …

I would recommend moving your code into more dedicated classes. Sending emails has nothing to do with Schedulable. Usually imho a Schedulable class should just look like: public class MySchedulable i …

Change your access modifier from global to public. Based on the comments, that fixes the issue.