APEX Scheduler Queue Confirmation

Question

I wanted to double check on my scheduler to make sure is was compiled correctly. I need it to run every minute, which is not possible, so I have it scheduled for every 15 minutes. Testing is difficult because I have to wait 15 minutes every time I want to test one change. Is there a way around this?

While I am waiting for the newest change I wanted to check with you guys to see if everything looked okay. I am getting failed Status Details but because the limit is 255 characters, I am unable to see the entire failure string. So I am trying to troubleshoot (slowly...every 15 minutes. sadface). Also, why is it skipping scheduled job 1?

Apex:

global class AutoStartSchedulerUpdateStageName {
   global void AutoStartSchedulerUpdateStageName() {}

   public static void start()
   {
       System.schedule('Scheduled Job 1', '0 0 * * * ?', new AutoStartScheduler());
       System.schedule('Scheduled Job 2', '0 15 * * * ?', new AutoStartScheduler());
       System.schedule('Scheduled Job 3', '0 30 * * * ?', new AutoStartScheduler());
       System.schedule('Scheduled Job 4', '0 45 * * * ?', new AutoStartScheduler());
   }
}

global class AutoStartScheduler implements Schedulable {

    global void execute(SchedulableContext SC) {
        AutoStartSchedulerLogic a = new AutoStartSchedulerLogic();
    }
}

global with sharing class AutoStartSchedulerLogic {
    global AutoStartSchedulerLogic(){
        List<Opportunity> brokerAPIOppty = [SELECT Id FROM Opportunity WHERE CreatedBy.Name = 'nfapi Site Guest User' AND StageName = 'Identified' AND RecordType.Name = 'Broker WC Oppty'];
        if(!brokerAPIOppty.isEmpty()){
            for(Opportunity o : brokerAPIOppty) {
                o.StageName = 'Statements In - MCA';
            }
            update brokerAPIOppty;
        }
    }
}

UPDATE: Triggers and Callouts dislike each other so a future method is needed. Future methods can't return values back into the flow because of sync/async issues. All other workarounds (ie: updating a field in sf with the webservice values etc..) caused order of execution issues/"uncommitted work pending".

The ideal flow we need is:

1. Third Party Insert
2. REST service calls apex class
3. apex updates Opportunity field
4. Opportunity Trigger fires
5. class is called
   • this class calls the flow and passes input parameters
6. flow is called
7. flow wait element is called
8. flow calls an apex class that:
   • webservice is called in this class
   • platform events are created in this class
9. flow resumes when platform event is published
10. continues logic...

Two callouts are creating the loop error.

Answer 1

Your first job is set to run on the zero minute of the hour, which is exactly what your screenshot shows it doing. If you schedule it when you're already past the zero minute, Salesforce does not run it immediately. (That behavior is not analogous to time-based workflow rules).

As far as testing goes, you absolutely can test scheduled jobs in an Apex unit test by scheduling the job between Test.startTest() and Test.stopTest(). This will force the job to run synchronously.

Additionally, since you've wisely broken your logic out into a handler class, you can unit test the handler class separately to determine why you're getting errors. Unit testing will also generate logs you can inspect to view error details.

A couple notes on code style:

• You don't need to check whether the list is empty before iterating over it. (It will not be null).
• It's generally considered unwise to perform DML in a class initializer. I'd suggest making the method that performs work in your handler class a static method, since it does not need to maintain state.
• You're mixing global and public access modifiers. These classes should be public unless you have a specific reason they need to be global.

Lastly, and most importantly: why is this a scheduled class rather than a trigger or workflow rule?

Answer 2

Too long for a comment.

1. Don't use the global access modifier unless you need it!
   • You almost never and definitely not for Schedulable implementations, let alone classes they call further down the chain.
2. You haven't included any logic which cannot be implemented just as well or better in a trigger.
   • If you are using a Schedulable implementation to escalate privileges, consider using Platform Events instead.
3. You can just test your service level logic directly without waiting for the schedule to run. Just go to Execute Anonymous and run the same logic you have in your execute block.
   • Testing via anonymous scripts has the added advantage of being able to wrap the logic in a try/catch block.
   • It will be easier to catch debug logs for a transaction you actively initiate.
4. Checking if the list is empty doesn't add any value.
   • Looping through an empty list has no cost.
   • DML Statements against an empty list are free.
5. Don't use stateful methods when you have no state.
   • Mark your AutoStartSchedulerLogic method as static
   • Give it a return type (e.g. void) so it is no longer a constructor.
   • Try coming up with a more informative name, like promoteStage or some such.