- Starting from release 1.7 JobScheduler requires a database to be available. The previously available feature to fallback to logging its history to CSV files and to continue processing in case of database failures is not available any longer.
- The settings in factory.ini for need_db= and db_max_errors= would not cause a running JobScheduler to continue in case of database failure.
- The JobScheduler always waits for the database to become available
- Deprecated, Unsupported: Release 1.7
- Removed: Release 1.10