You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
People already get too much email; we don't want to make the problem worse.
Reminders are not very intelligent – when running over a very short timeframe, people get emails telling them to submit their project when the system isn't even available to them yet.
Reminders can be sent very close together when running over a short timeframe (e.g. 14-day and 7-day reminders being sent simultaneously, if the deadline is set for less than a week away at rotation creation).
The Graduate Office is bcc'd into every email – is this actually what they want? (also: do users expect that the Graduate Office can e.g. read feedback from supervisors to students, given the access controls the backend imposes on that data?)
The text was updated successfully, but these errors were encountered:
Previously, one job would be scheduled for each "pester point" of a
deadline. Combined with the very long misfire_grace_time, this would
result in several reminders being sent simultaneously if they were
scheduled in the past, and in that case the notification would also
state the wrong number of days left (since the delta was hardcoded).
Now, each deadline's reminders are contained within a single job, which
is triggered at several predefined dates relative to the deadline. The
offset between the job and the deadline is calculated when the reminder
is sent, and if two reminders are scheduled to run simultaneously (e.g.
the 14-day and 7-day reminders), only the most recent reminder will be
sent (see #12).
Fixes#7.
People already get too much email; we don't want to make the problem worse.
Reminders can be sent very close together when running over a short timeframe (e.g. 14-day and 7-day reminders being sent simultaneously, if the deadline is set for less than a week away at rotation creation).The Graduate Office is bcc'd into every email – is this actually what they want? (also: do users expect that the Graduate Office can e.g. read feedback from supervisors to students, given the access controls the backend imposes on that data?)The text was updated successfully, but these errors were encountered: