CiviCRM Scheduled Reminders, Effective Start Date and Effective End Date are incorrectly evaluated if these fields contain a value '0000-00-00 00:00:00'
CiviCRM Scheduled Reminders, Effective Start Date and Effective End Date are incorrectly evaluated if these fields contain a value '0000-00-00 00:00:00'. This causes the Scheduled Reminder to not be sent, because the Effective Start Date and Effective End Date then are added to the query for the date comparison.
This has been observed on a CiviCRM system where the rows for Scheduled Reminders had values of '0000-00-00 00:00:00' for both the effective_start_date and effective_end_date columns. Using CiviCRM 5.40.1 and MariaDB 10.3.
There is no issue when effective_start_date and effective_end_date has null as the value.
This problem relates to this PR https://github.com/civicrm/civicrm-core/pull/19973
Agileware Ref: CIVICRM-1820