dschibster / sfdx-batch-orchestrator

A fork of the Salesforce Labs unmanaged Package for organizing Batch Jobs and their Schedules via a record-based Scheduling Configuration, including dependencies and ad-hoc runs.

_{Icons (Clock, Database) made by dmitri13 and Smashicons from www.flaticon.com}

Installation

For your Sandbox:

SFDX Batch Orchestrator

This is a fork from the original Apex Batch Job Scheduler from Salesforce Labs, including several improvements.

Features

• Configuration of Batch Job Schedules from within a Salesforce App
• Options to configure Hourly, Daily, Weekly, Monthly or Yearly schedules, with automatic generation of Cron Expressions
• If the options presented don't fit, you can also write your own Cron Expression!
• If you already have a Batch Job running, you can even incorporate it without much hassle!
• Grouping of Batch Jobs to handle dependencies
• Flexible switching of Batch Sizes in case of scaling problems
• Logging of Batch Job results to see if they were successful
• Options to directly run any Batch Job or Schedule that is currently scheduled from the UI
• Enhanced Logging! Now allows you to log information and successes/failures in a Batch Job. More information available in the Documentation.

Documentation

The documentation has moved! Please refer to the project GitHub Page of this repository here: https://dschibster.github.io/sfdx-batch-orchestrator

sfdx-batch-orchestrator's Issues

Issue Title

Log retention Dates + Automatic Deletion of Batch Job Logs

Ideas:

• Custom Setting to configure Retention Time
• Option to remove everything or only Logs that have no errors inside

Enable possibility to schedule several times an hour

This requires more than one Scheduled Job to be able to do "normally". The other option would be to try and reschedule in the finish() section of a batch job to run after one of the jobs is done running.

Create Promotion pipeline for pull requests / pushes to master

Package creation and promotion is a different beast from just running tests. This I need to check more thoroughly.

Possibility to start Jobs from a Flow Action

This is to make it easier to incorporate the Batch Jobs in Flows that you might want to create on your own. Will also make it possible to start the PoC with sub-hourly schedules.

Notify Users when a Batch Job has failed Batches / fails completely.

MIXED_DML_OPERATION

BatchJobLogger throws an error with the "logLegacy" method.

System.DmlException: Failed to save batch job log: Insert failed. First exception on row 0; first error: MIXED_DML_OPERATION, DML operation on setup object is not permitted after you have updated a non-setup object (or vice versa): Batch_Job_Log__c, original object: User: []

The error comes from:
Class.BatchJobLogger.logLegacy: line 183, column 1

This actually happened while running one of our test-classes.
Is there anything we can do here?

Inactive Batch Job Groups in a Schedule lead to the next Jobs being skipped

Log into Nebula Logger

Hey Dennis,

awesome tool from an awesome guy 😉

we have several batch jobs scheduled which is working fine. But for logging, we are using Nebula Logger since the tool is more sophisticated for logging. Is it possible to combine both? The batch job logs can show whether the job was successfull, but Nebula allows us to log business logic related issues, but there we don't see whether the job was successful. It would be great to allow users to select the logging system.

Process could look like:

1. Batch Orchestrator starts with a job.
2. In the code of the job, we are using Logger.info to log stuff
3. Job was successful, so Orchestrator marks the log as successful (or at least, not as an error)
4. Both information (Status of job + business logic) is stored in one log

If business logic calls Logger.error(), the job/log should be marked as failed.