Each job gets its own unique ID, differentiated by the parameters.
Observed Behaviour
The three jobs share the same ID.
Possible Solutions
The Job ID is created using a hash that takes into account the first two parameters that are passed to the \GO\Job constructor (i.e. $command and $args), while allowing the ID to be overridden by the supplied identifier, if any.
Environment
composer require peppeocchi/php-cron-scheduler:^3.0
How to reproduce
Expected Behaviour
Each job gets its own unique ID, differentiated by the parameters.
Observed Behaviour
The three jobs share the same ID.
Possible Solutions
The Job ID is created using a hash that takes into account the first two parameters that are passed to the
\GO\Job
constructor (i.e.$command
and$args
), while allowing the ID to be overridden by the supplied identifier, if any.