Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

2
  • 1
    I'd say that "something going terribly wrong" would be unlikely. Recall that start, (each call to) execute and finish are invoked in isolated transactions so finish should still be called. Now, your finish code could violate governor limits at which point the scheduling of the next invocation could easily be rolled back and you are left with no batch running at all. Commented Mar 31, 2021 at 15:47
  • You could consider using Queueables for this instead. Once the Transaction Finalizer GAs this would be a robust way to handle things (albeit without the easy System.scheduleBatch "pause" between executions). Commented Mar 31, 2021 at 15:49