Dynamic as in you don't need to predefine the task in a config file or decorator before you start your server.

This way you can load and unload tasks at runtime based on user input which you can optionally and independently save in your own database.

Like imagine a user wanting to control when a backup happens. You can ask them to fill out a form on your site to say "ok run this every day at 4am" and that would spawn a new job that executes at that interval and the user can also delete that and the job would be removed. There might be 100 different users each with their own individual backup jobs that are running or not running.