Timeline for Bug? Same Batch Can Be Run From Cron & Schedule Apex
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 13, 2017 at 12:54 | history | edited | CommunityBot | replaced http://salesforce.stackexchange.com/ with https://salesforce.stackexchange.com/ | |
| Dec 28, 2016 at 16:22 | comment | added | Adrian Larson♦ | Only someone with the Author Apex permission can schedule a job, generally. These users should be trusted to do the right thing. If someone is scheduling jobs via the System.schedule method when they should not, you have a people problem, not a platform problem. | |
| Dec 28, 2016 at 16:19 | comment | added | DJD | And Adrian, agree on you can schedule as many jobs as we want dah! But my point is should it allow duplicates to run at the same time for example batch1 to run at 6AM for a given apex class and batch2 to run at same 6AM for same given apex class. Then definitely we will end up with row locks and it is a waste of resources. | |
| Dec 28, 2016 at 16:19 | comment | added | Adrian Larson♦ | In your particular case, it may be a waste of resource, but often it is not. This behavior is WAD. | |
| Dec 28, 2016 at 16:16 | comment | added | DJD | If you try scheduling the same job from UI, it would throw an error complaining about being duplicate. That is why my whole point started does or should SalesForce has a right mechanism to find duplicates and complain about them. It is a waste of processing time and records will be locked anyways by doing so. | |
| Dec 28, 2016 at 16:12 | history | answered | Adrian Larson♦ | CC BY-SA 3.0 |