is it possible to force consume a task list ?

[jvancoillie]

Let me explain, I have a task list configured to be executed each month 0 0 1 * * (is the @monthly expression available ?) see below

# config/packages/scheduler.yaml
scheduler_bundle:
    transport:
        dsn: 'doctrine://default?execution_mode=first_in_first_out&table_name=scheduler_tasks&auto_setup=false'
    tasks:
        activation:
            type: 'command'
            command: 'app:activation'
            description: 'activate params'
            single_run: true
            output: true
            output_to_store: true
            priority: 1
            tags: ['api']
        etablissements:
            type: 'command'
            command: 'app:etablissements'
            expression: '0 0 1 * *'
            description: 'Import des établissements'
            output: true
            tags: ['api']
        communes:
            type: 'command'
            command: 'app:communes'
            expression: '0 0 1 * *'
            description: 'Import des communes'
            output: true
            tags: ['api']

and I would need that at the first execution of the scheduler:consume for example a deployment on the 15th of the month that the tasks are automaticaly executed.

do I have to switch to a single_run configuration like this

# config/packages/scheduler.yaml
scheduler_bundle:
    transport:
        dsn: 'doctrine://default?execution_mode=first_in_first_out&table_name=scheduler_tasks&auto_setup=false'
    tasks:
        deploy:
            type: 'chained'
            single_run: true
            tasks:
                activation:
                    type: 'command'
                    command: 'app:activation'
                    description: 'activate params'
                    output: true
                    output_to_store: true
                    priority: 1
                etablissements_single_run:
                    type: 'command'
                    command: 'app:etablissements'
                    single_run: true
                    description: 'Import des établissements'
                    output: true
                    tags: ['api']
                communes_single_run:
                    type: 'command'
                    command: 'app:communes'
                    description: 'Import des communes'
                    output: true
                    tags: ['api']
        etablissements:
            type: 'command'
            command: 'app:etablissements'
            expression: '0 0 1 * *'
            description: 'Import des établissements'
            output: true
            tags: ['api']
        communes:
            type: 'command'
            command: 'app:communes'
            expression: '0 0 1 * *'
            description: 'Import des communes'
            output: true
            tags: ['api']

[Guikingone]

Hi @jvancoillie 👋🏻

Thanks for the question 🙂

is the @monthly expression available ?

Yes, as defined in the Expression.

And I would need that at the first execution of the scheduler:consume for example a deployment on the 15th of the month that the tasks are automatically executed.

Using single_run can be a solution (thanks to the chained type), I don't have a "rocket-science based" solution but I'm thinking about using tags (maybe @deploy) which can be used via scheduler:consume with an extra option (maybe --tags @deploy), any thoughts? 🤔

[jvancoillie]

Why not the additional option --tags perhaps interesting to execute a group of tasks.
Will this option have the possibility of executing a group of tasks instantly ?

The --force option can also be interesting if you want to force the execution of a task without taking into account the expresssion configuration but this option does not solve my scenario which would be to execute the list of tasks without last execution date when setting up the cron.
It's annoying to have to wait 1 month for a @monthly configuration. indeed the single_run could meet my need, nevertheless I have a multiplication of the configuration of the same task.

I don't have a "rocket-science based" too, I feed the thinking ...

[Guikingone]

It could be an idea to have an extra command called scheduler:execute where we execute tasks depending on a set of options (maybe with tags, expression, name and so on), this approach can separate the "consuming" and the "execution" (where you can call this command whenever you need it).

The --force option can also be interesting if you want to force the execution of a task without taking into account the expression configuration

I'm not a big fan of this as this could force us to filter a second time the tasks depending on the transport list, this could introduce a new call and I try to limit the performances impact as much as possible.

[jvancoillie]

Nice, scheduler:execute with options to select the task(s) would be a great feature !