Description

I've talked to a few users who keep their scheduled tasks in a database and want to use scheduler to run them. This is not easily possible now as the schedules are set when first runningmessenger:consume scheduler_default.

Within the current scheduler architecture, what would be required to achieve this? I'm don't have a great understanding of the deep scheduler internals (the trigger heap system).

Example

class MyScheduleimplements ScheduleProviderInterface{publicfunctiongetSchedule():Schedule    {$schedule =newSchedule();// fetch tasks from db and add to schedule as recurring messagesreturn$schedule;    }}