Version 4.1
- Helper for using a version of the scheduler in unit/integration tests is now available in the artifact, through the class
TestHelper.createManualScheduler(...)
. For usage example seeSchedulerClientTest
. - It is now possible to manually trigger a check for due executions in the database. Of course, if this is done too frequently there will be an increased overhead.
- The scheduler can be instructed to do a best-effort attempt at executing executions it sees is being scheduled to run
now()
or earlier through the builder-methodenableImmediateExecution()
. - Bugfix:
scheduler.getScheduledExecutionsForTask(...)
was not working properly