This issue is similar to what happened with my ticket from a year or so ago to attempt to get Yealink phones modified to not always reboot when a new config is pushed from EPM.
Developers took the posted issue and made a change without a cohesive thought for the rest of the ecosystem.
In my case instead of adding a new context to send a different SIP notify, they simply changed the existing [reboot-yealink] to not actually reboot. Leaving the thing doing something other than what it is named.
I blame myself, after the fact, for not posting a more thought out bug report.
This change to cron stuff is similar. It should never happen if there is only one cron for all the things.
If an admin uses time conditions and calendars to change call flow on a schedule, does that now mean those are also varied by 30 seconds?
System crons for status or health or anything else are not important crons. Those can run whenever.
But when an admin schedules a task for 5:02 and 5:05, those need to fire at exactly 5:02 and 5:05.
Edit: The same thing also happened with the change to the IVR functionality. It asn’t until it was posted here in the community that they stopped and added the “Legacy” handling for digit matching.