Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
Description
We notice that after deploying the service all subsequent scheduler triggers after the very first one are incorrectly marked as reminders even when they are for "original" events. This is a result of re-using the same JobDataMap and Properties object between the original and reminder Jobs for the Scheduler. The following changes create deep copies of both to use for the reminders so adding a reminder flag in one will not affect the other.