Currently, every time a webform is updated, all of its scheduled emails are marked as needing to be rescheduled at the next cron run. See webform_scheduled_email_entity_update(). This can be disruptive and even cause all previously-scheduled-for-send emails to not go out if the next cron run happens after the scheduled send date and the ignore_past setting is TRUE.
It would be nice if this reschedule-after-webform-update behavior was optional so:
1. People might be more aware of this default behavior from the outset (I was not expecting it).
2. Those of us who do not need it and/or find it disruptive could turn it off.
1. Queue up some scheduled emails for send.
2. Make a small update to the webform.
3. See that all scheduled emails are now marked WebformScheduledEmailManagerInterface::SUBMISSION_RESCHEDULE.
Make rescheduling after webform entity update optional.
Idea acceptance, patch/MR, review.
New option either in the webform or handler's config.
None.
None.
Active
6.2
Code
Here's an initial patch that makes rescheduling after webform / source entity updates optional. Needs review.
The feature request makes sense. We will need to implement this via 6.3.x and create an MR with some test coverage.