With Winter '27 developer console has been replaced by Web Console. That's all fine & dandy.
My problem is that my practice has been to schedule batch processes to run as another user -- essentially a service user that doesn't change with staffing changes. I would log in as that user, open developer console and run a "{class_name}.scheduleMe();" method that would add the job to the apex job schedule.
It appears that when logged in as another user and launching the new Web Console I can no longer use Execute Anonymous. (I *can* create a script and run execute anonymous if I have NOT logged in as someone else.) The user I'm logging in as has the same authority as myself.
#Salesforce Developer
I think I found a way around this. It'll take a small modification to all my batch job classes and my self-scheduler class, but it achieves something else I've always wanted.
Each batch process has a "control" record where I can provide and adjust parameters to control how it runs, batch size, etc (or skip running by de-selecting the "Active" flag).
If I make each of these batch jobs implement a SelfScheduler interface that has the "scheduleMe" method, then I can create a flow action button on these control records that pass the record Id to an invocable method that reads the class name of the control record, instantiates it and invokes the scheduleMe() method ... something like this:
for(ControlRcd__c cr : [SELECT BatchClassName__c FROM ControlRcd__c WHERE Id in :rcdIds) {
SelfScheduler ss = (SelfScheduler) Type.forName(cr.BatchClassName__c).newInstance();
ss.scheduleMe();
}
This way I can still simply log in as our service user, click the scheduleMe button on the control record and the new schedule will be under the running user.
