I understand that the reason for this is that restarting the job in the Queue Manager is not making a new submission, as such the craft/queue run isn't executed until another job is submitted.
I don't expect there is a workaround for this, but wondered if it might be worth adding a button "Run queue" to the plugin?
Would just help user experience for non-developer site admins.
I guess those users don't have access to the Craft Admin (CP) > admin/utilities/async-queue-test?
If they have access, they can hit the [Run test] button to trigger a queue/run.
I understand that the reason for this is that restarting the job in the Queue Manager is not making a new submission, as such the craft/queue run isn't executed until another job is submitted.
I don't expect there is a workaround for this, but wondered if it might be worth adding a button "Run queue" to the plugin?
Would just help user experience for non-developer site admins.
Unless you have a better idea? :)