feature: allow scheduling of scheduled tasks

[M-arcus]

No description provided.

[M-arcus]

[schneider-felix]

Doesn't really matter here but I wanted to point it out anyways. Set task status to scheduled immediately will not work when using the symfony scheduler bridge in shopware. The symfony scheduler stores its own lastExecutionTime and ignores the values from the database.

[shyim]

can we not overwrite the data of symfony scheduler?

[schneider-felix]

can we not overwrite the data of symfony scheduler?

I don't think so. The only way to do this is to dispatch the message manually to the message bus. The scheduler keeps information about lastRun in a local variable. And with this PR shopware/shopware#5456 it also writes it to cache. But it will never update the DB.

On the other hand when using the symfony scheduler, the status will also never change to queued/failed. It will always remain in the scheduled state. This is because the bridge never updates this value. It just checks for it.

[M-arcus]

Maybe it should be dispatched immediately inside the scheduleTask function?
Like in https://github.com/shopware/shopware/blob/trunk/src/Core/Framework/MessageQueue/ScheduledTask/Scheduler/TaskScheduler.php#L147

[schneider-felix]

Nevermind, I was wrong about this altogether xD. It will always run, even if it is in the queued or failed state. The only exception is the inactive state. See here: https://github.com/shopware/shopware/blob/3d2e531639877ff0d839b98fc6081beec0cd5ebf/src/Core/Framework/MessageQueue/ScheduledTask/SymfonyBridge/ScheduleProvider.php#L46

[M-arcus]

@schneider-felix

Nevermind, I was wrong about this altogether xD.

So the current state of the scheduling code in this PR is correct?

It will always run, even if it is in the queued or failed state.

Is this intended behaviour?

The only exception is the inactive state

Sounds like new PR I can create :D setInactive or sth

[schneider-felix]

Personally I would not put too much thought into this. Symfony scheduler bridge is currently marked experimental. There are some things that are quite broken about it currently but no one really seems to care (I pointed some of those things out in my PR but it was just merged without even talking about them :D). Scheduler Bridge will break other thinks in FroshTools anyways (like overdue scheduled tasks). So I would just merge it for now.

What do you think @shyim ?