Open
Description
Symfony version(s) affected
6.4.1/7.0.1
Description
There is a bug in the Symfony Scheduler component where the cache TTL is erroneously set to a value less than a Scheduler's Message Frequency.
This causes the Scheduler to not dispatch any recurring messages at all.
Using a Cache with a TLL less than a Scheduler's Message Frequency is obviously wrong.
There should be no TTL at all, but it seems Scheduler should be able to handle this the same as a cache miss at continue producing messages as if there was no cache used.
How to reproduce
Follow reproduction steps at https://github.com/bendavies/symfony-bug-52911
Possible Solution
Not really sure?
- Fix the bug so a cache miss (from a ttl expiry) does not stop recuring messages being generated.
- Warn if the provided cache has a default ttl? (should be zero for scheduler?).
- manually set
$item->expiresAfter(0)
at ?
Additional Context
No response